Adobe Launch Logo Adobe Experience Platform Launch

    • Light
    • Dark

Error Handling

When a problem occurs in Launch, an error may be returned in one of the following ways:

API response

When performing an API request that results in an immediate error, an error response will be returned by the API, with the HTTP code reflecting the general type of error that occured.

Resource meta

When performing an API request that results in a delayed error, an asynchronous activity for example, an error may be returned by the API in the {"meta": {"status_details": ... }} of a related resource.

Error Format

Error responses aim to conform to the JSONAPI Errors specification, and will generally adhere to the following structure:

  • id: a unique identifier for this particular occurrence of the problem.
  • status: the HTTP status code applicable to this problem, expressed as a string value.
  • code: an application-specific error code, expressed as a string value.
  • title: a short, human-readable summary of the problem that SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization.
  • detail: a human-readable explanation specific to this occurrence of the problem. Like title, this field’s value can be localized.
  • source: an object containing references to the source of the error, optionally including any of the following members:
    • pointer: a JSON Pointer [RFC6901] to the associated entity in the request document [e.g. “/data” for a primary data object, or “/data/attributes/title” for a specific attribute].
  • meta: a meta object containing non-standard meta-information about the error.

For example:

  "errors": [
      "id": "8a5526da-ab12-4be9-b084-2efe537f388c",
      "status": "404",
      "code": "not-found",
      "title": "Record Not Found",
      "meta": {
        "request_id": "jfb0dQ2e0XVTkQ6AOfEJFfTDjguw9x3d"
      "source": {



Your IMS access token is invalid. You can get a new access token by signing in again. Or for technical accounts, generating a new JWT and swapping for an IMS access token.


A connection to the server could not be established.


The data could not be decrypted with the provided passphrase.


The data could not be decrypted with the provided private key. Ensure the key works locally and that whitespace has been trimmed.


The data cannot be decrypted without a private key. Please provide an encryped private key.


The extension did not provide the expected definition of this delegate descriptor. The extension may need to be updated.


The resources that you are trying to add to your Library have been deleted.


An Environment can only be assigned to one Library at a time. Option 1 is to choose a different environment. Option 2 is to free up this Environment by moving the Library to another Environment or deleting the Library.


Your Library must have an Environment assigned before you can create a Build.


The extension that defines a data element or rule component is not included in the library. Ensure that all the required extensions have been added to your library.


A path defined in extension.json was incorrectly constructed.


You have defined an invalid transform for an object property. Each object property can have one transform defined and it must be a file transform or a function transform.


An error occurred while unzipping the ExtensionPackage or zipping the files for distribution.


A Host may not be deleted if one or more Environments are using it.


The Environment assigned to this Library does not have a valid Host. Check which Environment is assigned to your Library. Then assign a valid Host to that Environment.


Only SFTP Hosts need to have credentials verified before they can be used, so the pretest is only available for that Host type.


You are not allowed to use the customCode transform. Please specify a function or file transform.


An unknown error occurred authorizing your account. Please try again later.


There is an issue with the signed-in session. Please log out and log in again.


An internal error occurred. Please wait a few minutes and try again. If the issue persists, please contact Client Care.


An invalid data element cannot be added to a library.


Either this is not a valid DTM embed code or you're trying to link it to a Launch Development or Staging Environment. DTM embed codes can only be linked to Launch Production Environments.


An invalid extension cannot be added to a library.


You can only modify some of the object properties of an Extension Package. You tried to modify one of the ones that is not allowed.


The Org ID you tried to assign is not a valid Org ID.


Your active Org doesn't have Launch access. Check that you're using the correct Org.


An invalid rule cannot be added to a library.


A syntax error was encountered while parsing the settings JSON.


A required file defined in extension.json could not be found inside the zip package.


The code could not be compiled due to invalid code or ES6 code.


Only one revision of each resource can be included in a library.


This user account does not belong to a product profile that has access to Launch. Use the Admin Console to add this user to a product profile with Launch rights.


This user account does not have the necessary permissions to perform this action.


The record could not be found. Verify the id of the object that you're trying to retrieve.


The name you are trying to use is already in use. For this resource, the 'name' property must be unique.


Public release of extensions is coordinated by


This resource is read-only and cannot be modified.


The user session has expired. Please log out and log in again.


Authentication failed for the SFTP connection.


The SFTP connection has timed out.


An exception was encountered when using SFTP to connect to the server.


An SFTP exception was encountered while trying to communicate with the server.


A socket error was encountered while trying to communicate with the server.


The SSH session was disconnected.


The connection with the server timed out.


An unexpected error occurred. You can try again later or give Customer Care a call and explain what you were doing when it happened.


A custom code language was supplied that is not supported.


Once you've installed an extension upgrade, you must include it in all Libraries until the upgrade gets to Production. The only exception is if the extension has not been published yet.


A successful Build for the upstream Library is required before you can build this one.