Agentforce Data Library Errors

The Agentforce Data Library service manages data libraries, sources, retrievers, and file uploads for use in Agentforce agents. Errors from this service typically indicate that a requested resource wasn’t found, that a permission or prerequisite is missing, that a request field failed validation, or that a provisioning operation encountered a temporary failure.

This error code indicates an unexpected system error and not an issue with your configuration. If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: BLOCKED_BY_FAILURE
• Any context that might help with the investigation, such as when the error occurred, what you or your end user were doing at the time, and whether you’re able to reproduce it

You can’t disable a data category while selections still reference it. Remove all references to the data category first, then retry the disable operation.

This error occurs when:

• One or more sources still have data category selections that reference the category you’re trying to disable.

To resolve this error:

1. List the sources that currently reference this data category.
2. Remove the data category selections from those sources.
3. Retry the disable operation.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: DATA_CATEGORY_DISABLED_WITH_SELECTIONS

The data category ID in your request doesn’t exist in this org. Verify the ID and try again.

This error occurs when:

• The dataCategoryId doesn’t match any data category in this org.
• The data category was deleted after the identifier was captured.
• The data category exists in a different org or dataspace than the one being targeted.

To resolve this error:

1. Look up the data category in Setup and copy the current ID.
2. Verify the request is targeting the correct org and dataspace.
3. Try again with the correct dataCategoryId.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: DATA_CATEGORY_ID_NOT_FOUND

The data category selections in your request conflict with each other. Choose a non-conflicting combination and try again.

This error occurs when:

• Two data category selections in the request can’t be combined per the category rules.
• A parent-child data category relationship makes both selections invalid together.

To resolve this error:

1. Review the data category rules and identify which selections are mutually exclusive.
2. Choose one non-conflicting combination.
3. Try again.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: DATA_CATEGORY_MUTUALLY_EXCLUSIVE

The data category name in your request doesn’t exist in this org. Data category names are case-sensitive. Verify the name and try again.

This error occurs when:

• The dataCategoryName doesn’t match any data category in this org.
• There’s a typo or casing mismatch in the name.
• The data category was renamed after the name was captured.

To resolve this error:

1. Look up the data category in Setup and copy the current name exactly.
2. Confirm the name’s casing matches the value in Setup.
3. Try again with the correct dataCategoryName.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: DATA_CATEGORY_NAME_NOT_FOUND

The data category configuration you requested isn’t supported for this source type. Check which source types accept data category configuration and adjust your request.

This error occurs when:

• The source type doesn’t accept data category configuration.
• The requested data category is scoped to a different source type than the one in the request.

To resolve this error:

1. Check the documentation for which data category configurations each source type supports.
2. Either use a source type that supports the requested configuration, or remove the data category configuration from this source.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: DATA_CATEGORY_NOT_SUPPORTED

The required data category rule isn’t enabled for your org. Ask your Salesforce admin to enable it in Setup, then try again.

This error occurs when:

• The data category rule is defined but not enabled for the org.
• The rule was disabled by an admin after being previously enabled.

To resolve this error:

1. Ask your Salesforce admin to enable the required data category rule in Setup.
2. Once the rule is enabled, try again.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: DATA_CATEGORY_RULE_NOT_ENABLED

This operation requires a data category selection, but none was provided. Add a selection and try again.

This error occurs when:

• The operation depends on a data category selection and none was provided.
• The selection was cleared by an earlier update and never restored.

To resolve this error:

1. Add a data category selection to the request.
2. Try again.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: DATA_CATEGORY_SELECTION_REQUIRED

Agentforce Data Library doesn’t support companion orgs directly. To connect to a companion org, use a custom retriever instead.

This error occurs when:

• Your org is a Data 360-enabled companion org, which doesn’t support Agentforce Data Library operations.

To resolve this error:

1. Use a custom retriever to link to the companion org.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: DC1_NOT_SUPPORTED
• The org ID

Data 360 asset provisioning failed. This is usually a temporary issue. Wait a moment and try again.

This error occurs when:

• A temporary issue occurred during Data 360 asset provisioning.
• The provisioning service was temporarily unavailable.

To resolve this error:

1. Wait a moment and try again.
2. If the error persists, contact Salesforce Customer Support.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: DC_ASSET_FAILED
• The approximate time the error occurred (UTC) and the library name or ID the provisioning was targeting

The Data 360 connection isn’t active yet. Wait for Data 360 provisioning to complete, then try again.

This error occurs when:

• Data 360 was just enabled and its connection is still being set up.
• The Data 360 connection was interrupted and hasn’t reconnected.

To resolve this error:

1. Wait a few minutes for Data 360 provisioning to complete.
2. Try again once the Data 360 connection is active.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: DC_CONNECTION_MISSING

The resource can’t be deleted because another resource is currently using it. Remove or update the references first, then try again.

This error occurs when:

• The resource is referenced by another resource that must be removed or updated first.
• A dependent resource still points to this one.

To resolve this error:

1. Identify the resources that reference this one and remove or update those references first.
2. Try again once no other resource points to it.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: DELETE_IN_USE

A content field appears more than once in your request. Each content field must be unique.

This error occurs when:

• The same content field is listed twice in the request.
• Two content field entries resolve to the same underlying field.

To resolve this error:

1. Remove duplicate content field entries from the request.
2. Confirm each content field is listed exactly once.
3. Try again.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: DUPLICATE_CONTENT_FIELDS

Another file with the same name already exists on this source. Use a unique file name and try again.

This error occurs when:

• A file with the same fileName was already uploaded to this source.
• A prior upload of the same file didn’t complete cleanly and left a partial record.
• Two parallel uploads used the same file name.

To resolve this error:

1. Rename the file locally and retry the upload, or delete the existing file with the same name first.
2. If the duplicate is leftover from a failed upload, remove it before continuing.
3. Try again with a unique fileName.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: DUPLICATE_FILE_NAME

More than one field in your request is marked as primary, but only one primary field is allowed.

This error occurs when:

• Two or more fields in the request are flagged as primary.
• A prior primary field wasn’t cleared before marking a new one.

To resolve this error:

1. Review the request and confirm exactly one field is marked as primary.
2. Clear the primary flag on all other fields.
3. Try again.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: DUPLICATE_PRIMARY_FIELDS

Agentforce Data Library isn’t enabled for your org. Ask your Salesforce admin to enable it, then try again.

This error occurs when:

• The Agentforce Data Library feature isn’t enabled in your org’s setup.

To resolve this error:

1. Ask your Salesforce admin to enable Agentforce Data Library for your org.
2. Once it’s enabled, try again.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: FEATURE_NOT_ENABLED
• The org ID and the operation you were attempting

One or more files referenced in your request aren’t present in storage. The upload either didn’t start or didn’t complete for those files. Waiting and retrying the same request won’t create the missing files. You need to upload them again first.

This error occurs when:

• A file upload URL was obtained but the file was never uploaded to it.
• The upload to the file upload URL failed and the failure wasn’t surfaced.
• The file was uploaded to a different URL than the one referenced in this request.
• The filePath in the request was copied from a different session and doesn’t correspond to a completed upload.

To resolve this error:

1. Don’t retry the same request. Waiting won’t create the missing file.
2. Request a fresh file upload URL and upload the file to it. Confirm the upload completed successfully.
3. Reference the newly uploaded file in a new request.
4. If uploads keep failing, verify network connectivity and that the file meets the size and content-type requirements for the upload URL.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: FILES_NOT_UPLOADED
• The filePath values that failed, and the upload URL used to try to upload each one (if known)

This operation requires at least one file, but none were provided.

This error occurs when:

• The request omitted the file list entirely.
• The file list was present but empty.
• An upstream step was expected to attach files and didn’t.

To resolve this error:

1. Attach at least one file to the request.
2. If files come from an upstream step, verify that step produces a non-empty result before this operation runs.
3. Try again.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: FILES_REQUIRED

The number of files in this request exceeds the per-request limit. Split the files across multiple requests and try again.

This error occurs when:

• The request included more files than the per-request maximum.

To resolve this error:

1. Split the files across multiple requests, keeping each under the maximum file count.
2. Submit the requests separately.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: FILE_LIMIT_EXCEEDED

File migration to the upstream store failed. This is usually a temporary issue. Wait a moment and try again.

This error occurs when:

• A temporary issue occurred during file migration.
• The upstream storage service was temporarily unavailable.

To resolve this error:

1. Wait a moment and try again.
2. If the error persists, contact Salesforce Customer Support.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: FILE_MIGRATION_FAILED
• The approximate time the error occurred (UTC) and the library name or ID and the affected files (if known)

The file you requested doesn’t exist on the specified source. Verify the file identifier and try again.

This error occurs when:

• The fileId in the request doesn’t match any file on the target source.
• The file was deleted or replaced after the identifier was captured.
• The fileId is correct but belongs to a different source than the one in the request path.

To resolve this error:

1. Look up the current files on the target source and copy the correct fileId.
2. Confirm the file belongs to the source referenced in the request.
3. Try again with the correct fileId.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: FILE_NOT_FOUND

The file path you provided isn’t valid for your user context. The path must reference a location within your own Data 360 file storage root.

This error occurs when:

• The file path points to a location outside your accessible file storage.
• The file path belongs to another user’s storage area.
• A stale or absolute path was used from a different user context.

To resolve this error:

1. Check that the file path resolves within your own accessible storage area.
2. If you need to share files across users, ask the owning user to reference them from their own context.
3. Try again with a corrected file path.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: FILE_PATH_OWNERSHIP

Document indexing failed for one or more files. This is usually a temporary issue. Wait a moment and try again.

This error occurs when:

• A temporary issue occurred during document indexing.
• The indexing service was temporarily unavailable.

To resolve this error:

1. Wait a moment and try again.
2. If the error persists, contact Salesforce Customer Support.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: INDEXING_FAILED
• The approximate time the error occurred (UTC) and the library name or ID and the affected files (if known)

This error code indicates an unexpected system error and not an issue with your configuration. If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: INTERNAL_ERROR
• Any context that might help with the investigation, such as when the error occurred, what you or your end user were doing at the time, and whether you’re able to reproduce it

The description you provided exceeds the maximum allowed length. Shorten it and try again.

This error occurs when:

• The description text is longer than the maximum allowed character count.

To resolve this error:

1. Shorten the description to fit within the maximum length.
2. Try again.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: INVALID_DESCRIPTION

The developer name you provided doesn’t meet Salesforce naming rules. Correct the name and try again.

This error occurs when:

• The developerName contains characters other than letters, digits, and underscores.
• The name starts with a digit or underscore, or ends with an underscore.
• The name exceeds the maximum allowed length.

To resolve this error:

1. Use only letters, digits, and underscores in the developer name.
2. Start the name with a letter and keep it within the length limit.
3. Try again with a conforming developerName.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: INVALID_DEVELOPER_NAME

The field name you provided isn’t valid. Correct it and try again.

This error occurs when:

• The fieldName contains characters that aren’t allowed.
• The field name doesn’t match a known field on the target resource.
• There’s a typo or casing mismatch in the field name.

To resolve this error:

1. Check the field naming rules and the target resource’s field list.
2. Correct the fieldName value.
3. Try again.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: INVALID_FIELD_NAME

The field type you provided for this field isn’t supported. Correct it and try again.

This error occurs when:

• The field type supplied for fieldName isn’t one of the supported types.
• There’s a typo or casing mismatch in fieldType.
• The field type was valid at some point but has since been retired.

To resolve this error:

1. Check the Agentforce Data Library documentation for the supported field types.
2. Correct the fieldType value for the field named fieldName.
3. Try again.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: INVALID_FIELD_TYPE

The file name you provided contains disallowed characters or exceeds the maximum length.

This error occurs when:

• The fileName contains disallowed characters (for example, path separators or control characters).
• The name exceeds the maximum allowed length.
• The name is empty or consists only of whitespace.

To resolve this error:

1. Remove disallowed characters from the file name.
2. Shorten the name to fit within the maximum length.
3. Try again with a valid fileName.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: INVALID_FILE_NAME

The index mode you provided isn’t supported. Check the supported values and try again.

This error occurs when:

• The index mode value isn’t one of the supported options.
• There’s a typo or casing mismatch in the index mode value.

To resolve this error:

1. Check the documentation for the supported index modes.
2. Correct the index mode value.
3. Try again.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: INVALID_INDEX_MODE

The master label you provided is empty or exceeds the maximum allowed length.

This error occurs when:

• The masterLabel field was left blank.
• The label exceeds the maximum allowed character length.

To resolve this error:

1. Provide a non-empty master label.
2. Shorten the label to fit within the maximum length.
3. Try again.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: INVALID_MASTER_LABEL

The offset you provided is negative or exceeds the result set size. Provide a valid offset and try again.

This error occurs when:

• The offset is negative.
• The offset is greater than or equal to the total number of results.
• The request is paging past the end of the result set.

To resolve this error:

1. Set offset to a non-negative value less than the total result count.
2. If you’re at the end of the result set, stop paging.
3. Try again with a valid offset.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: INVALID_OFFSET

The page size you provided is outside the valid range. Provide a value between 1 and the maximum page size, then try again.

This error occurs when:

• The pageSize is less than 1 or greater than maxPageSize.
• The request is paging with a size the server no longer supports.

To resolve this error:

1. Set pageSize to a value between 1 and maxPageSize (inclusive).
2. If you need more results, page through them instead of requesting a larger single page.
3. Try again.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: INVALID_PAGE_SIZE

The source type you provided isn’t valid. Check the supported values and try again.

This error occurs when:

• The sourceType value isn’t one of the supported types.
• There’s a typo or casing mismatch in the source type value.
• The source type was valid at some point but has since been retired.

To resolve this error:

1. Check the Agentforce Data Library documentation for the current list of supported source types.
2. Correct the sourceType value to one of the supported values.
3. Try again.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: INVALID_SOURCE_TYPE

The source type filter you provided isn’t valid. Check the supported filter values and try again.

This error occurs when:

• The source type filter value isn’t one of the supported filter options.
• There’s a typo or casing mismatch in the filter value.

To resolve this error:

1. Check the documentation for the supported source type filter values.
2. Correct the filter to a supported value.
3. Try again.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: INVALID_SOURCE_TYPE_FILTER

The wait-max-time value you provided is outside the valid range. Check the supported range and try again.

This error occurs when:

• The waitMaxTime value is negative, zero, or exceeds the maximum allowed.
• A unit conversion mistake put the value in the wrong range (for example, milliseconds instead of seconds).

To resolve this error:

1. Check the documentation for the supported waitMaxTime range.
2. Set waitMaxTime to a value within the supported range.
3. Try again.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: INVALID_WAIT_MAX_TIME

A library with the name or identifier you provided already exists. Choose a different name or identifier and try again.

This error occurs when:

• The libraryName matches an existing library in this org.
• A prior create attempt succeeded partially and left an existing record.

To resolve this error:

1. Choose a unique libraryName and try again.
2. If a prior create was expected to fail, check whether the library was actually created and reuse it instead of creating a new one.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: LIBRARY_ALREADY_EXISTS

The data library you requested doesn’t exist in this org. Verify the library identifier and try again.

This error occurs when:

• The libraryId in the request doesn’t match any library in this org.
• The library was deleted or renamed after the identifier was captured.
• The request is being sent to a different org than the one where the library exists.

To resolve this error:

1. Look up the library in Agentforce and copy the current identifier.
2. Verify the request is targeting the same org the library belongs to.
3. Try again with the correct libraryId.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: LIBRARY_NOT_FOUND

The source type in your request doesn’t match the source type the existing source was created with. You can’t change a source’s type after creation.

This error occurs when:

• The request is trying to update an existing source with a different source type than it was created with.
• The sourceType field was accidentally changed on an update call.

To resolve this error:

1. Look up the existing source’s type and match it in the request.
2. If you need a different source type, delete the existing source and create a new one with the desired type.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: MISMATCH_SOURCE_TYPE

Your org doesn’t satisfy a required prerequisite for this operation. Ask your Salesforce admin to review and configure the prerequisites, then try again.

This error occurs when:

• Your org is missing a required permission, license, or dependent feature needed for this operation.

To resolve this error:

1. Ask your Salesforce admin to review the org’s Agentforce Data Library prerequisites and enable any missing ones (for example, required org permissions, license provisioning, or dependent features).
2. Once the prerequisite is in place, try again.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: MISSING_ORG_PREREQUISITE
• The org ID and the operation you were attempting

A required field is missing from your request. Add the field and try again.

This error occurs when:

• The fieldName shown in the error was omitted from the request.
• The field was present but set to an empty string or null.
• A typo in the field key caused the field to be skipped.

To resolve this error:

1. Add the required field (fieldName) to the request body.
2. Provide a non-empty value for the field.
3. Try again.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: MISSING_REQUIRED_FIELD

Agentforce Data Library operations are only supported in the default dataspace. There’s no configuration change that enables it in non-default dataspaces.

This error occurs when:

• The request is targeting a non-default dataspace, which isn’t supported by Agentforce Data Library.

To resolve this error:

1. Switch the request context to the default dataspace and try again.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: NON_DEFAULT_DATASPACE
• The dataspace and org ID

A content field in your request overlaps with another already configured on this source. Choose a non-overlapping field or remove the existing configuration first.

This error occurs when:

• The new content field resolves to the same underlying data as an already-configured content field.
• Two content fields cover the same field path with different labels.

To resolve this error:

1. Review the existing content fields on the source and identify the overlap.
2. Choose a non-overlapping content field, or remove the existing configuration before adding the new one.
3. Try again.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: OVERLAPPING_CONTENT_FIELD

You don’t have permission to perform this operation on the specified Agentforce Data Library resource. Contact your Salesforce admin to grant access.

This error occurs when:

• The acting user doesn’t have the permission required for this Agentforce Data Library operation.

To resolve this error:

1. Ask your Salesforce admin to grant the permission required for Agentforce Data Library operations on the affected resource.
2. Confirm you’re authenticated as the correct user before trying again. The permission is checked against the acting user, not the org.
3. If access was recently granted, sign out and sign back in so the session picks up the updated permissions.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: PERMISSION_DENIED
• The Salesforce user and the resource you were trying to access

Primary fields can’t be modified after a source is created. If you need a different primary field, delete and recreate the source.

This error occurs when:

• The update request tries to change which field is marked primary on an existing source.
• The primary field configuration was regenerated on the client and no longer matches the source.

To resolve this error:

1. Keep the existing primary field configuration on the source.
2. If you need a different primary field, delete and recreate the source with the desired configuration.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: PRIMARY_FIELDS_IMMUTABLE

Library provisioning is still in progress. Wait a few minutes and try again.

This error occurs when:

• The library was recently created and its backing infrastructure is still being provisioned.
• Provisioning is running longer than usual for this org.

To resolve this error:

1. Wait a few minutes and try again.
2. Poll the library’s status until it reaches the ready state before proceeding.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: PROVISIONING_IN_PROGRESS

Retriever provisioning failed. This is usually a temporary issue. Wait a moment and try again.

This error occurs when:

• A temporary issue occurred during retriever provisioning.
• The provisioning service was temporarily unavailable.

To resolve this error:

1. Wait a moment and try again.
2. If the error persists, contact Salesforce Customer Support.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: RETRIEVER_FAILED
• The approximate time the error occurred (UTC) and the library name or ID the retriever provisioning was targeting

The retriever you requested is currently inactive. Activate it before issuing this request.

This error occurs when:

• The retriever exists but is in an inactive state.
• The retriever was deactivated by an admin after being previously active.

To resolve this error:

1. Activate the retriever in Agentforce.
2. Try again once the retriever is active.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: RETRIEVER_NOT_ACTIVE

The retriever you requested doesn’t exist. Verify the retriever identifier and try again.

This error occurs when:

• The retrieverId in the request doesn’t match any retriever in this org.
• The retriever was deleted after the identifier was captured.
• The request is being sent to a different org than the one where the retriever exists.

To resolve this error:

1. Look up the retriever in Agentforce and copy the current retrieverId.
2. Verify the request is targeting the correct org.
3. Try again with the correct retrieverId.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: RETRIEVER_NOT_FOUND

Search index provisioning failed. This is usually a temporary issue. Wait a moment and try again.

This error occurs when:

• A temporary issue occurred during search index provisioning.
• The provisioning service was temporarily unavailable.

To resolve this error:

1. Wait a moment and try again.
2. If the error persists, contact Salesforce Customer Support.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: SEARCH_INDEX_FAILED
• The approximate time the error occurred (UTC) and the library name or ID the search index provisioning was targeting

Your org has reached the maximum number of search indexes allowed. Delete unused indexes to free up space, then try again.

This error occurs when:

• The org already has the maximum permitted number of search indexes.
• An older, no-longer-needed index is still occupying a slot.

To resolve this error:

1. Identify any search indexes that are no longer needed and delete them.
2. Try again once a slot is available.
3. If your workflow requires more indexes than the current quota allows, contact Salesforce Customer Support to discuss options.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: SEARCH_INDEX_QUOTA_EXCEEDED

The data source you requested doesn’t exist on the specified library. Verify the source identifier and try again.

This error occurs when:

• The sourceId in the request doesn’t match any source on the target library.
• The source was deleted, or a stale identifier is still in use.
• The sourceId is correct but belongs to a different library than the one in the request path.

To resolve this error:

1. Look up the current sources on the target library and copy the correct sourceId.
2. Confirm the source belongs to the library referenced in the request.
3. Try again with the correct sourceId.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: SOURCE_NOT_FOUND

The file type you provided isn’t supported by Agentforce Data Library. Convert the file to a supported format and try again.

This error occurs when:

• The file’s extension isn’t on the supported file type list.
• The file was renamed with an extension that misrepresents its actual content.

To resolve this error:

1. Check the documentation for the supported file types.
2. Convert the file to a supported format, or exclude it from this operation.
3. Try again with only supported file types.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: UNSUPPORTED_FILE_TYPE

The source type you provided isn’t currently supported by Agentforce Data Library.

This error occurs when:

• The source type is recognized as a valid identifier but isn’t yet enabled for Agentforce Data Library.
• The source type has been deprecated for Agentforce Data Library use.

To resolve this error:

1. Check the Agentforce Data Library documentation for the currently supported source types.
2. Choose a supported source type for this operation.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: UNSUPPORTED_SOURCE_TYPE

An update is already in progress on this resource. Wait for it to finish and try again.

This error occurs when:

• A previous update on the same resource hasn’t finished yet.
• Two clients issued updates against the same resource at the same time.

To resolve this error:

1. Wait for the in-progress update to finish before trying again.
2. If the update appears stuck, check the resource’s status to confirm it eventually reaches a terminal state.
3. Try again once the resource is idle.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: UPDATE_IN_PROGRESS

The upload isn’t ready for the requested operation yet. Wait for the upload to complete and try again.

This error occurs when:

• The upload was still in progress when the follow-up operation ran.
• The request ran too soon after the upload started.

To resolve this error:

1. Wait for the upload to reach the ready state before running the follow-up operation.
2. Check the upload status periodically. Wait a moment between checks.
3. Try again once the upload is ready.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: UPLOAD_NOT_READY

The upload didn’t become ready before the wait-max-time expired. Wait a while and try again. The upload may still complete on its own.

This error occurs when:

• The upload took longer than the configured waitMaxTime.
• The upload is still in progress and just needs more time.

To resolve this error:

1. If the upload is expected to take longer, increase waitMaxTime for this operation.
2. Wait and try again. The upload may complete on its own.
3. If the upload never completes, contact Salesforce Customer Support.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: UPLOAD_NOT_READY_TIMEOUT

j

Get Started

Agentforce Examples

Agent Script

Agentforce DX

Agentforce APIs and SDKs

Agentforce Actions

Agentforce Service Errors

Agent Service Reasoner Errors

Agentforce Data Library Errors

Authentication Service Errors

Bring Your Own Node Service Errors

General Agentforce Service Errors

Interactive Data Science Service Errors

Language Detection Service Errors

ML Lake Service Errors

Model Builder Errors

Prediction Service Errors

Models and Prompts

Headless Agentforce Development