# General Errors
General Errors
Section titled “General Errors”| Status | Detail | Description |
|---|---|---|
| 400 | Invalid request payload | An invalid request payload has triggered this generic error. Details on the specific invalid fields are often found in the error array |
| Status | Detail | Description |
|---|---|---|
| 401 | Access token expired | The authorization header Bearer token used in the request is expired. |
| Status | Detail | Description |
|---|---|---|
| 403 | Not authorized to perform the action | The caller is not authorized to perform the operation on the resource. It indicates the caller does not have enough permisssion(ACL) set on the resource or its parent |
| Status | Detail | Description |
|---|---|---|
| 404 | Requested URL not found | Either the endpoint is not correct or the requested resource is not available in the system |
| Status | Detail | Description |
|---|---|---|
| 500 | Server error occurred | This error indicates the request is valid but some exception occured in the server side |
| Status | Detail | Description |
|---|---|---|
| 503 | Service unavailable | The service is temporarily unavailable due to maintenance, overloading, or other internal system issues. Please retry your request after a brief delay, and if the problem persists, contact system administrators. |
| Status | Detail | Description |
|---|---|---|
| 409 | Conflict with the current state of the resource | The requested operation cannot be performed because it conflicts with the current state of the resource. This typically occurs when multiple users attempt to modify the same resource simultaneously or when a resource has been modified since it was last retrieved. |
| Status | Detail | Description |
|---|---|---|
| 401 | Not authorized to perform the action | The user or application does not have sufficient permissions to perform the requested action. Ensure you have the proper authentication credentials and the required roles assigned to your account. |
| Status | Detail | Description |
|---|---|---|
| 401 | Authorization headers are missing in the request | The request is missing the required authorization headers needed to authenticate the user. Include a valid Bearer token in the Authorization header of your request. |
| Status | Detail | Description |
|---|---|---|
| 400 | Invalid page size, page size should be between 1 and 1000 | The page size parameter specified in the request is outside the allowed range. Adjust your page size parameter to be between 1 and 1000 and retry the request. |
| Status | Detail | Description |
|---|---|---|
| 405 | Method not allowed for the requested URL | The HTTP method used in the request is not supported for the specified endpoint. Check the API documentation for the correct HTTP method (GET, POST, PATCH, DELETE, etc.) to use with this URL. |
| Status | Detail | Description |
|---|---|---|
| 400 | Account id should not exceed 50 characters | The account ID provided in the request exceeds the maximum allowed length of 50 characters. This typically occurs during the create space request. |
| Status | Detail | Description |
|---|---|---|
| 400 | Invalid next page token | The pagination token provided for retrieving the next set of results is invalid or has expired. Request a new pagination token by making a fresh request or start from the beginning of the result set. |
| Status | Detail | Description |
|---|---|---|
| 400 | Type error occurred | A data type mismatch or conversion error occurred while processing the request. Verify that all parameters have the correct data types as specified in the API documentation and that your values can be properly converted to the expected types. |
| Status | Detail | Description |
|---|---|---|
| 400 | Invalid path param | One or more path parameters in the request URL are invalid or malformed. Check the format and constraints of all path parameters according to the API documentation and ensure they meet the required specifications. |
| Status | Detail | Description |
|---|---|---|
| 400 | Invalid query param | One or more query parameters in the request URL are invalid or contain unsupported values. Verify that all query parameters conform to the allowed values and formats specified in the API documentation. |
| Status | Detail | Description |
|---|---|---|
| 400 | Invalid restore request | The request to restore a resource contains invalid parameters or conflicts with the current state of the system. Ensure the resource is in a deleted state and that all parameters in the restore request are valid and complete. |
| Status | Detail | Description |
|---|---|---|
| 415 | Content-Type header was not ‘application/json’ | The request was sent with an incorrect or missing Content-Type header value. Set the Content-Type header to ‘application/json’ for all requests that include a JSON payload in the request body. |
| Status | Detail | Description |
|---|---|---|
| 400 | The request can include either the If-Match header or the If-None-Match header, but not both | The request included both If-Match and If-None-Match. Remove one of these headers and try again. |
| Status | Detail | Description |
|---|---|---|
| 400 | Invalid If-Match header | The If-Match header format is invalid. |
| Status | Detail | Description |
|---|---|---|
| 400 | Invalid If-None-Match header | The If-None-Match header format is invalid. |
| Status | Detail | Description |
|---|---|---|
| 404 | Resource not found | This error code is used when a resource is not found. This error may occur immediately after creating a resource due to the file service’s eventual consistency. |
| Status | Detail | Description |
|---|---|---|
| 400 | Parent folder not found | This error code is used when a parent folder is not found. This error typically occurs in create operations such as create upload or create folder when the given parentId is not present or the in deleted state |
| Status | Detail | Description |
|---|---|---|
| 403 | Permission error | The caller does not have sufficient permissions to perform the requested operation on the resource. Verify that the caller has the appropriate role (contentManager, contentContributor, etc.) assigned for the action being attempted. |
| Status | Detail | Description |
|---|---|---|
| 400 | Resource cannot be restored on a deleted parent | Parent folder or space of the resource being restored is in a deleted state. The target parentId must be restored first or change the parentId. |
| Status | Detail | Description |
|---|---|---|
| 400 | Resource cannot be moved to the same parent | The parentId specified in the move operation is the same as the current parentId. Specify a different target folder to perform a move operation. |
| Status | Detail | Description |
|---|---|---|
| 400 | Name or path conflict occurred | The resource with the same name already exists at the specified path or location. Choose a different name for the resource or specify a different target location to resolve the conflict. Most likely this occurs due to concurrent operations on a same resource. The error will return the existing resource with the same name at the specified location. |
| Status | Detail | Description |
|---|---|---|
| 400 | Resource cannot be updated with the same ACL | The ACL applied to the resource in the payload is identical to the existing ACL. Make changes to the ACL before attempting to update the resource. |
| Status | Detail | Description |
|---|---|---|
| 400 | Resource cannot be updated with the same metadata | The custom metadata in the request payload is identical to the existing metadata. Make changes to the metadata before attempting to update the resource. |
| Status | Detail | Description |
|---|---|---|
| 403 | Permission error on the resource with ACL | The caller(user, application or device) does not have sufficient permissions to modify the ACL on the resource. Only callers with contentManager or higher roles can modify access control settings. |
| Status | Detail | Description |
|---|---|---|
| 400 | Name conflict | A resource with the same name already exists in the target location. Choose a different name for the resource or specify a different target location to resolve the conflict. |
| Status | Detail | Description |
|---|---|---|
| 400 | Full path exceeds the maximum length | The complete path of the resource, including folder hierarchy, exceeds the maximum allowed length. Reduce the path length by using shorter folder or file names, or by reducing the nesting depth. |
| Status | Detail | Description |
|---|---|---|
| 400 | Actor not found in existing resource ACL. Remove operation cannot be performed | The specified actor is not present in the ACL of the resource, so it cannot be removed. Verify that the actor identifier is correct and that the actor is currently in the ACL list. |
| Status | Detail | Description |
|---|---|---|
| 400 | Actor already present in existing resource ACL. Add operation cannot be performed | The specified actor is already present in the ACL of the resource with the specified role. To update the role, use the proper update operation instead of attempting to add a duplicate entry. |
| Status | Detail | Description |
|---|---|---|
| 400 | The original location of the resource is not available. Parent has been either moved or renamed | The resource cannot be restored to its original location because the parent folder has been moved, renamed, or deleted. Specify a new location for restoring the resource or restore the parent folder first. |
| Status | Detail | Description |
|---|---|---|
| 400 | Role not found in the existing resource ACL. Remove operation cannot be performed | The specified role is not found in the ACL of the resource for the given actor. Verify that the role specified in the remove operation matches the currently assigned role. |
| Status | Detail | Description |
|---|---|---|
| 400 | ACL not found in the existing resource. Remove operation cannot be performed | The resource does not have any ACL entries that match the specified criteria for removal. Verify that the resource has ACL entries before attempting to remove them. |
| Status | Detail | Description |
|---|---|---|
| 400 | One of the parent of the resource is in deleted state or under the deletion process | The operation cannot be completed because one of the parent resource is either deleted or in the process of being deleted. Restore the parent resource before retrying the operation. |
| Status | Detail | Description |
|---|---|---|
| 409 | It’s possible that multiple resources share the same path. Adjust the parameters to obtain the correct result. | This error occurs when multiple resources are found to have the same path. Verify the resource identifiers and adjust the request parameters to get the targeted resource. |
| Status | Detail | Description |
|---|---|---|
| 412 | The provided match header condition did not match the current resource state | This error occurs when the condition specified in the match header (If-Match or If-None-Match) does not align with the current state of the resource. Verify the resource’s state and update the match header condition accordingly before retrying the operation. |
| Status | Detail | Description |
|---|---|---|
| 400 | Expiration cannot be set on a support file | Support files do not support the expiresAt field. Remove expiresAt from the request or set it on the parent. |
| Status | Detail | Description |
|---|---|---|
| 409 | Resource is checked out | The resource is checked out and cannot be modified. Check it in before retrying the modification. |
| Status | Detail | Description |
|---|---|---|
| 409 | Resource is not checked out | Only resources that are already checked out can be checked in back. |
| Status | Detail | Description |
|---|---|---|
| 403 | One or more actors outside the space membership boundary are not permitted because their roles are not in the allowedRolesOutsideBoundary list. | When updating ACLs, each role assigned to a user outside the boundary group must appear in spaceMembershipBoundary.allowedRolesOutsideBoundary. Add the role to that list on the space or assign a permitted role. |
| Status | Detail | Description |
|---|---|---|
| 403 | One or more actors in the ACL are not permitted because they are not members or subgroups of the space boundary group | One or more actors in the ACL are not part of the space boundary group. Only boundary-group members can be added to the ACL. |
| Status | Detail | Description |
|---|---|---|
| 403 | Anonymous access cannot be set on the resource because allowAnonymousShares is disabled in the space | Enable allowAnonymousShares on the space to allow anonymous access. |
| Status | Detail | Description |
|---|---|---|
| 403 | Cannot modify or delete ACL entry owned by another application | The ACL entry you are trying to modify or delete is owned by a different application. Only the owning application can modify its own ACL entries. |
| Status | Detail | Description |
|---|---|---|
| 400 | Resource cannot be updated with the same expires_at | The expiresAt in the request payload is identical to the existing expiresAt. Make changes to the expiresAt before attempting to update the resource. |
| Status | Detail | Description |
|---|---|---|
| 403 | Permission denied: Access outside the space membership boundary is disabled | The user does not have permission to access this resource because access from outside the space membership boundary is not allowed. Contact the space administrator. |
| Status | Detail | Description |
|---|---|---|
| 400 | Unsupported file type for summarization. Supported types are: .csv, .doc, .docx, .html, .md, .pdf, .txt, .xls, .xlsx | The file extension is not supported for AI summarization. Ensure the file has one of the supported document formats. |
| Status | Detail | Description |
|---|---|---|
| 400 | File extension is missing. Summarization requires a file with a supported extension | The file name does not have an extension. Rename the file to include a supported extension before summarizing. |
| Status | Detail | Description |
|---|---|---|
| 404 | No current summary found. Call /summarize first | A summary has not been generated for this file version yet. Call the /summarize endpoint to initiate processing. |
| Status | Detail | Description |
|---|---|---|
| 400 | File summarization is not supported for Azure | AI summarization is currently only supported for spaces hosted on AWS. Azure spaces cannot be summarized. |
| Status | Detail | Description |
|---|---|---|
| 400 | A resource with this customId already exists | A resource with the specified custom identifier already exists in the system. Use a unique ID. |
| Status | Detail | Description |
|---|---|---|
| 422 | Document is too large to summarize | The textual content of the document exceeds the context token limit for the summarization model. Truncate or split the document into smaller parts. |
| Status | Detail | Description |
|---|---|---|
| 400 | File content cannot safely be processed | The document content was flagged by AI safety filters or prompt injection detection and cannot be processed safely. |
| Status | Detail | Description |
|---|---|---|
| 400 | File size exceeds the maximum allowed for summarization | The file exceeds the maximum allowed file size of 50 MB for summarization. Reduce the file size and retry. |
| Status | Detail | Description |
|---|---|---|
| 400 | File must have a clean malware scan status to be summarized | The file has not completed malware scanning or was flagged as infected. Wait for a CLEAN scan status before summarizing. |
| Status | Detail | Description |
|---|---|---|
| 400 | Actor/role combination matches only app-owned ACL entries, which must be removed by id | The targeted ACL entry is owned by an application. To modify or remove this entry, provide its unique id in the request. |
| Status | Detail | Description |
|---|---|---|
| 400 | One or more ids not found in existing resource ACL | The specified ACL entry identifier was not found on the resource. Verify the entry ID from the resource’s current ACL. |
| Status | Detail | Description |
|---|---|---|
| 422 | File contains no extractable content to summarize | The file appears to be empty, scanned without OCR text, or contains no readable textual content that can be passed to the model. |
Space Errors
Section titled “Space Errors”| Status | Detail | Description |
|---|---|---|
| 400 | Invalid action query parameter, action should be (copy|create) | The action query parameter provided in the request contains an invalid value. Use only ‘copy’ or ‘create’ as valid values for the action parameter. |
| Status | Detail | Description |
|---|---|---|
| 400 | Action query parameter is not allowed for patch operation | The action query parameter is not applicable for PATCH requests. Remove the action parameter when performing update operations on a space. |
| Status | Detail | Description |
|---|---|---|
| 400 | Space already exists | A space with the same identifier already exists in the system. Use a different identifier or retrieve the existing space if needed. |
| Status | Detail | Description |
|---|---|---|
| 404 | Space not found | The requested space does not exist or has been deleted. Verify the space identifier is correct and the space has not been removed. |
| Status | Detail | Description |
|---|---|---|
| 403 | Space is not active | The requested space is in a deleted or inactive state and cannot be accessed. Restore the space first if it has been soft-deleted, or create a new space if it was permanently deleted. |
| Status | Detail | Description |
|---|---|---|
| 404 | Parent path does not exist | The specified parent path for the operation does not exist in the system. Create the parent path first or specify a valid existing path. |
| Status | Detail | Description |
|---|---|---|
| 500 | Space creation failed | This error indicates the request is valid but some exception occured in the server side during space creation. |
| Status | Detail | Description |
|---|---|---|
| 500 | Space update failed | This error indicates the request is valid but some exception occured in the server side during space update. |
| Status | Detail | Description |
|---|---|---|
| 500 | Space delete failed | This error indicates the request is valid but some exception occured in the server side during space deletion. |
| Status | Detail | Description |
|---|---|---|
| 400 | Space is not empty | The space contains files or folders and cannot be deleted without the recursive parameter. Set recursive=true to delete a non-empty space. |
| Status | Detail | Description |
|---|---|---|
| 400 | Cannot restore an active space | The space is already in an active state and does not need to be restored. Restoration operations are only applicable to deleted spaces. |
| Status | Detail | Description |
|---|---|---|
| 400 | Space name already exists | A space with the same name already exists in the account. Choose a different name for the space to avoid conflicts. |
| Status | Detail | Description |
|---|---|---|
| 400 | Minimum a space manager is required in the space. Update operation cannot be performed | At least one user must have the space manager role in a space at all times. Ensure your update operation maintains at least one space manager. |
| Status | Detail | Description |
|---|---|---|
| 400 | At least one space manager without accessExpiresAt is required | At all times, a space must have at least one space manager without accessExpiresAt. Ensure your update preserves at least one such space manager. |
| Status | Detail | Description |
|---|---|---|
| 400 | Space cannot be updated with the same deletion retention | The update operation specifies the same deletion retention period as the current setting. Specify a different retention period or omit this parameter if no change is intended. |
| Status | Detail | Description |
|---|---|---|
| 400 | Space cannot be updated with the same storage mode | The update operation specifies the storage mode as the current setting. Specify a different storage mode or omit this parameter if no change is intended. |
| Status | Detail | Description |
|---|---|---|
| 409 | Operation not allowed: Space is read-only | The Space is in read-only mode. The intented operation is restricted. |
Folder Errors
Section titled “Folder Errors”| Status | Detail | Description |
|---|---|---|
| 400 | Invalid folder path | The folder path provided in the request is invalid or malformed. Check that the path follows the correct format, does not contain invalid characters, and starts with a forward slash. |
| Status | Detail | Description |
|---|---|---|
| 400 | Folder already exists | A folder with the same name already exists at the specified location. Choose a different name or location to create the folder. |
| Status | Detail | Description |
|---|---|---|
| 400 | Either target_id or target_path is required | The request is missing both target_id and target_path parameters. Provide either target_id or target_path to identify the destination. |
| Status | Detail | Description |
|---|---|---|
| 400 | Name is required for rename action | The rename operation is missing the required name parameter. Provide a valid name for the folder when performing a rename operation. |
| Status | Detail | Description |
|---|---|---|
| 400 | Archive is required for archive action | The archive operation is missing the required archive parameter. Provide valid archive information when performing an archive operation. |
| Status | Detail | Description |
|---|---|---|
| 404 | Folder does not exist | The requested folder does not exist or has been deleted. Verify the folder identifier or path is correct and that the folder exists. |
| Status | Detail | Description |
|---|---|---|
| 400 | Action query param is required for folder operation either create or copy | The request is missing the required action query parameter. Specify either ‘create’ or ‘copy’ as the action parameter for folder operations. |
| Status | Detail | Description |
|---|---|---|
| 400 | Invalid query parameter {query_param}, {query_param_value} should only be in {query_param_value_list} | The specified query parameter value is not among the allowed values. Refer to the allowed value list in the error message and use only those valid values. |
| Status | Detail | Description |
|---|---|---|
| 400 | Metadata or acl field required | The request body is missing both metadata and acl fields. Include at least one of these fields when updating a folder. |
| Status | Detail | Description |
|---|---|---|
| 400 | copyAcl param cannot be true when permissionsLocal given | The request includes copyAcl=true and permissionsLocal. Only one is allowed for a copy operation. Remove copyAcl when explicit permissions are provided. |
| Status | Detail | Description |
|---|---|---|
| 400 | Folder already exists | A folder with the same name already exists at the specified location. Choose a different name or location to avoid conflicts. |
| Status | Detail | Description |
|---|---|---|
| 404 | Folder not found | The requested folder does not exist or has been deleted. Verify the folder identifier is correct and that the folder exists. |
| Status | Detail | Description |
|---|---|---|
| 400 | Parent folder cannot be moved to children | The target location is a child (or descendant) of the source folder. A parent folder cannot be moved into its own subtree. Choose a different destination. |
| Status | Detail | Description |
|---|---|---|
| 403 | Folder is not active | The folder is in a deleted or inactive state and cannot be accessed. Restore the folder first if it has been soft-deleted. |
| Status | Detail | Description |
|---|---|---|
| 400 | Folder is not empty | The folder contains files or subfolders and cannot be deleted without the recursive parameter. Set recursive=true to delete a non-empty folder. |
| Status | Detail | Description |
|---|---|---|
| 400 | Root folder cant be deleted | The root folder cannot be deleted |
| Status | Detail | Description |
|---|---|---|
| 400 | Folder is not empty | The folder contains files or subfolders and cannot be deleted without the recursive parameter. Set recursive=true to delete a non-empty folder. |
| Status | Detail | Description |
|---|---|---|
| 400 | Root folder can’t be moved | This error indicates the resource is a root folder, which is not allowed to be moved. |
| Status | Detail | Description |
|---|---|---|
| 400 | Root folder can’t be renamed | This error indicates the resource is a root folder, which is not allowed to be renamed. |
| Status | Detail | Description |
|---|---|---|
| 400 | Path should begin with a forward slash(/) | The path in the request is invalid because it must start with a forward slash (/). |
| Status | Detail | Description |
|---|---|---|
| 400 | Cannot restore as folder with same name exists | A folder with the same name already exists at the restoration location. Choose a different name or location for the restored folder. |
| Status | Detail | Description |
|---|---|---|
| 400 | Path already exists | A folder or file with the same path already exists in the system. Choose a different path to avoid conflicts. |
| Status | Detail | Description |
|---|---|---|
| 409 | It’s possible that multiple folders share the same path. Adjust the parameters to obtain the correct result. | Multiple resources may share the same path (for example, a deleted folder and an active folder). When fetching by path without a status filter, the result can be ambiguous. Specify status=active or use the folder ID to retrieve the correct resource. |
| Status | Detail | Description |
|---|---|---|
| 400 | Folder cannot be copied to itself or its subfolder | The target location for the copy operation is the source folder itself or one of its subfolders. Select a different target location outside the source folder hierarchy. |
| Status | Detail | Description |
|---|---|---|
| 400 | Root folder can’t be copied | This error indicates the resource is a root folder, which is not allowed to be renamed. |
| Status | Detail | Description |
|---|---|---|
| 400 | Can only restore a soft deleted folder | The restore operation can only be performed on folders that have been soft-deleted and are within their retention period. Permanently deleted folders cannot be restored. |
| Status | Detail | Description |
|---|---|---|
| 400 | Root folder doesn’t have versions | The root folder does not support versioning. |
File Errors
Section titled “File Errors”| Status | Detail | Description |
|---|---|---|
| 400 | Either (path and spaceId) or fileId is mandatory. Both cannot be given | The request contains both fileId and (path and spaceId) parameters, which are mutually exclusive. Provide either fileId or the combination of path and spaceId, but not both. |
| Status | Detail | Description |
|---|---|---|
| 400 | Either (path and spaceId) or fileId is mandatory | The request is missing both fileId and (path and spaceId) parameters. Provide either fileId or the combination of path and spaceId to identify the file. |
| Status | Detail | Description |
|---|---|---|
| 400 | Space id is required when path is provided | The request includes a path parameter but is missing the required spaceId parameter. Always include the spaceId when using a path to identify a file. |
| Status | Detail | Description |
|---|---|---|
| 400 | File path is required | The request is missing the required path parameter. Provide a valid file path when using path-based operations. |
| Status | Detail | Description |
|---|---|---|
| 400 | Mandatory Fields are required | The request is missing one or more required fields. Check the API documentation to ensure all mandatory fields are included in the request. |
| Status | Detail | Description |
|---|---|---|
| 400 | Invalid query parameter action, should only be in (move, rename, restore) | The action query parameter provided contains an invalid value. Use only ‘move’, ‘rename’, or ‘restore’ as valid values for file operations. |
| Status | Detail | Description |
|---|---|---|
| 400 | Either targetParentPath or targetParentId is mandatory. Both cannot be given | The request contains both targetParentPath and targetParentId parameters, which are mutually exclusive. Provide either targetParentPath or targetParentId, but not both. |
| Status | Detail | Description |
|---|---|---|
| 400 | Response headers can only be customized for restricted_access files. | The request attempts to customize response headers for a file that is not marked as restricted_access. Only files with restricted_access set to true can have customized response headers. |
| Status | Detail | Description |
|---|---|---|
| 400 | copyAcl param cannot be true when permissionsLocal given | The request includes copyAcl=true and permissionsLocal. Only one is allowed for a copy operation. Remove copyAcl when explicit permissions are provided. |
| Status | Detail | Description |
|---|---|---|
| 400 | File already exists | File with the same name already exists at the specified location. Choose a different name or location to avoid conflicts. |
| Status | Detail | Description |
|---|---|---|
| 400 | File not found | This error code is used when a file is not found. This error may occur immediately after creating a file due to the file service’s eventual consistency. |
| Status | Detail | Description |
|---|---|---|
| 400 | Cannot copy file as the file is already exists in destination path | File with the same name already exists at the specified location. Choose a different name or location to avoid conflicts. |
| Status | Detail | Description |
|---|---|---|
| 400 | Cannot move the file as the file exists in the destination folder | File with the same name already exists at the specified location. Choose a different name or location to avoid conflicts. |
| Status | Detail | Description |
|---|---|---|
| 400 | Can only restore a soft deleted file | The restore operation can only be performed on files that have been soft-deleted and are within their retention period. Active or permanently deleted files cannot be restored. |
| Status | Detail | Description |
|---|---|---|
| 400 | File creation failed | The system unable to create the file due to an internal error. Probably due to concurrent create file operation or the parent folder might have deleted at time of content upload. |
| Status | Detail | Description |
|---|---|---|
| 400 | Fileset creation failed | The system unable to create the fileset due to an issue with the archive extraction or validation. Verify that the archive file is valid and not corrupted. |
| Status | Detail | Description |
|---|---|---|
| 404 | File version not found | The requested file version was not found. |
| Status | Detail | Description |
|---|---|---|
| 400 | Cannot restore as file with same name exists | File with the same name already exists at the restoration location. Choose a different name or location for the restored file, or delete the existing file first. |
| Status | Detail | Description |
|---|---|---|
| 400 | Cannot rename as a file with the same name exists | The provided new name already exists in the same folder. Choose a different name or move the existing file before attempting the rename operation. |
| Status | Detail | Description |
|---|---|---|
| 409 | It’s possible that multiple files share the same path. Adjust the parameters to obtain the correct result. | Multiple resources may share the same path (for example, a deleted file and an active file). When fetching by path without a status filter, the result can be ambiguous. Specify status=active or use the file ID to retrieve the correct resource. |
| Status | Detail | Description |
|---|---|---|
| 409 | File is locked | The file is currently locked by another user and cannot be modified. Wait for the lock to be released or contact the user who locked the file. |
| Status | Detail | Description |
|---|---|---|
| 400 | File is not locked | The file not currently locked, so an unlock operation cannot be performed. Only locked files can be unlocked. |
| Status | Detail | Description |
|---|---|---|
| 400 | Links limit exceeded. Max of 10 allowed | Files has the maximum allowed number of support file links (10). Remove some existing links before adding new ones. If the request payload does not have 10 links, then check the existing links as well. |
| Status | Detail | Description |
|---|---|---|
| 400 | Resource cannot be updated with the same support file details | The support file details in the update or link request are identical to the existing details. Make changes to the support file details before attempting the update. |
| Status | Detail | Description |
|---|---|---|
| 404 | Support file not found | The provided support file ID is invalid, unavailable, or has been deleted. |
| Status | Detail | Description |
|---|---|---|
| 404 | Support file version is deleted | The provided support file ID has been deleted. |
| Status | Detail | Description |
|---|---|---|
| 400 | Support file is not a child of the main file | The file specified in the operation’s parentId and the main file id are different. The support files’ parentId should be same as the main file id. |
| Status | Detail | Description |
|---|---|---|
| 400 | Link operation cannot be performed on a support file | The link operation is only valid for main files, not support files. Support files cannot have links to other files. |
| Status | Detail | Description |
|---|---|---|
| 400 | Cannot modify a support file | The modify operation applies only to main files, not support files. Modifying a main file also updates its support files. |
| Status | Detail | Description |
|---|---|---|
| 400 | Cannot restore a support file | The restore operation applies only to main files, not support files. Restoring a main file also restores its support files. |
| Status | Detail | Description |
|---|---|---|
| 400 | Cannot delete a support file | The delete operation applies only to main files, not support files. Deleting a main file also deletes its support files. |
| Status | Detail | Description |
|---|---|---|
| 400 | Cannot copy an infected file | The file has been flagged as infected by the malware scanning system and cannot be copied. Infected files are restricted for security reasons. |
| Status | Detail | Description |
|---|---|---|
| 400 | ACL update operation cannot be performed on a support file | The support files inherit permissions from their parent file and cannot have their ACL settings modified directly. Update the parent file’s ACL instead. |
| Status | Detail | Description |
|---|---|---|
| 400 | Support file limit of 50 exceeded. | Max of 50 active support files (linked or unlinked) per parent file allowed. No more support files can be added to the given parent file. |
| Status | Detail | Description |
|---|---|---|
| 409 | File is checked out | The file is currently checked out by a user and cannot be modified. This conflict occurs when attempting to modify or delete a file that is in a checked-out state. Wait until the file is checked back in before attempting to modify it. |
| Status | Detail | Description |
|---|---|---|
| 400 | File is not checked out | The check-in operation cannot be performed because the file is not currently checked out. Only files that are in a checked-out state can be checked back in. |
| Status | Detail | Description |
|---|---|---|
| 400 | The operation you are trying to perform is only allowed on filesets | The requested operation is only applicable to filesets and cannot be performed on regular files. Ensure that the target resource is a fileset before attempting this operation. |
| Status | Detail | Description |
|---|---|---|
| 404 | Error fetching fileset manifest | The system was unable to retrieve the manifest for the requested fileset. The fileset may be corrupted or the manifest may be missing. |
| Status | Detail | Description |
|---|---|---|
| 403 | Cannot download infected file | The file has been flagged as infected by the malware scanning system and cannot be downloaded. Downloading infected files is restricted for security reasons. |
| Status | Detail | Description |
|---|---|---|
| 409 | Batch delete failed; one or more files have errors. | One or more files in the batch delete operation failed to be removed. Inspect the batch error details. |
| Status | Detail | Description |
|---|---|---|
| 409 | This file must be vectorized before it may be queried | The file has not been indexed into vector embeddings yet. Send a POST request to /vectorize and wait for completion before searching. |
| Status | Detail | Description |
|---|---|---|
| 500 | Vector search is not available for this space | The underlying vector index or search capability is not properly configured or is unavailable for this space. Contact support. |
| Status | Detail | Description |
|---|---|---|
| 400 | Your query could not be processed | The semantic search query could not be executed or was rejected by safety filtering. Refine your question and retry. |
| Status | Detail | Description |
|---|---|---|
| 404 | The specified path does not exist within the FileSet | The file path provided does not match any entry within the extracted fileset archive. |
| Status | Detail | Description |
|---|---|---|
| 400 | File size exceeds the maximum allowed for vectorization | The file exceeds the maximum allowed file size of 50 MB for vectorization. Reduce the file size and retry. |
| Status | Detail | Description |
|---|---|---|
| 400 | Unsupported file type for vectorization. Supported types are: .csv, .doc, .docx, .html, .md, .pdf, .txt, .xls, .xlsx | The file extension is not supported for vector embeddings indexing. Ensure the file has one of the supported document formats. |
| Status | Detail | Description |
|---|---|---|
| 400 | File extension is missing. Vectorization requires a file with a supported extension | The file name does not have an extension. Rename the file to include a supported extension before vectorizing. |
Object Errors
Section titled “Object Errors”| Status | Detail | Description |
|---|---|---|
| 400 | Object already exists | An object with the same identifier or path already exists. Choose a different identifier or location to avoid conflicts. |
| Status | Detail | Description |
|---|---|---|
| 404 | Object not found | The requested object does not exist or has been deleted. Verify the identifier or path. |
| Status | Detail | Description |
|---|---|---|
| 409 | It’s possible that multiple objects share the same path. Adjust the parameters to obtain the correct result. | Multiple objects may share the same path (for example, a deleted object and an active object). Specify status=active or use the object ID. |
| Status | Detail | Description |
|---|---|---|
| 400 | Schema validation failed | The request payload failed schema validation. Review the error details and correct the invalid fields. |
| Status | Detail | Description |
|---|---|---|
| 404 | Object version not found | The requested object version does not exist. |
| Status | Detail | Description |
|---|---|---|
| 403 | Object is not active | The object is deleted or inactive and cannot be accessed. Restore it to before retrying. |
| Status | Detail | Description |
|---|---|---|
| 400 | Can only restore a soft deleted object | The restore operation applies only to soft-deleted objects within their retention period. |
| Status | Detail | Description |
|---|---|---|
| 400 | Object cannot be updated with the same size or content | The update payload does not change the object’s size or content. Provide different content. |
| Status | Detail | Description |
|---|---|---|
| 400 | Cannot restore as object with same name exists | An object with the same name already exists at the restore location. Choose a different name or location. |
ACL Errors
Section titled “ACL Errors”| Status | Detail | Description |
|---|---|---|
| 403 | Application is not authorized to claim ACL ownership | The application is not authorized to use the ACL ownership feature. Only applications pre-authorized by File Service and registered in the service configuration can claim ownership of ACL entries. Contact the File Service team to request authorization for your application. |
Job Errors
Section titled “Job Errors”| Status | Detail | Description |
|---|---|---|
| 400 | Invalid job type, job type should be (SCAN) | Type specified in the request is invalid. Currently, only ‘SCAN’ is supported as a valid job type. (Deprecated) |
| Status | Detail | Description |
|---|---|---|
| 400 | Invalid Job type | Type provided in the request is not recognized by the system. Check the API documentation for the list of supported job types. (Deprecated) |
| Status | Detail | Description |
|---|---|---|
| 400 | Job already exist | The same parameters already exists and is currently running or queued. Wait for the existing job to complete before starting a new one. (Deprecated) |
Upload Errors
Section titled “Upload Errors”| Status | Detail | Description |
|---|---|---|
| 400 | Either (parentId and name) or path is mandatory | The request payload is missing both the (parentId and name) combination and the path parameter. Provide either the parentId and name combination or a complete path to identify the upload location. (Deprecated) |
| Status | Detail | Description |
|---|---|---|
| 400 | Either (parentId and name) or path is mandatory. Both cannot be given | The request payload contains both (parentId and name) and path parameters, which are mutually exclusive. Provide either (parentId and name) or path, but not both. (Deprecated) |
| Status | Detail | Description |
|---|---|---|
| 400 | For multipart upload completion, please give etag and part number information | The multipart upload completion request is missing the required etag and part number information. Include the etag and part number for each uploaded part in the completion request. Please note that if the space provider is azure, then there is strict validation on the etag and part number. |
| Status | Detail | Description |
|---|---|---|
| 400 | One of the part number or etag is missing in the parts list | All objects in the parts list for a multipart upload completion must include both a part number and an etag. Check that all entries have both fields properly specified. |
| Status | Detail | Description |
|---|---|---|
| 400 | Invalid url duration, url duration should be between 5m and 7d | The provided query parameter URL duration is outside the allowed range. Set the urlDuration parameter to a value between 5 minutes (5m) and 7 days (7d). |
| Status | Detail | Description |
|---|---|---|
| 500 | Unable to generate the upload URL | The service failed to generate a presigned upload URL. Retry the request. |
| Status | Detail | Description |
|---|---|---|
| 400 | Requested id is not a multipart upload | The provided upload ID is not associated with a multipart upload to complete the multipart patch. Verify the ID and retry. |
| Status | Detail | Description |
|---|---|---|
| 500 | upload_id is mandatory to generate the upload URL | Internal server error where upload URL cannot be generated, Retry the request. |
| Status | Detail | Description |
|---|---|---|
| 400 | Multipart upload completion failed due to an error. | The multipart completion failed. Retry the request |
| Status | Detail | Description |
|---|---|---|
| 400 | Support file fields provided for main file upload | The request payload contains support file fields but is attempting to create a main file. Remove the support file specific fields such as addToLinks. |
| Status | Detail | Description |
|---|---|---|
| 400 | ACL cannot be provided for a support file | The support files inherit permissions from their parent file and cannot have custom ACL settings. Remove the ACL field from the support file upload request. |
| Status | Detail | Description |
|---|---|---|
| 400 | Parent cannot be a support file | The requests attempts to upload a file with a support file as the parent. The parentId must be an id of a main file. |
| Status | Detail | Description |
|---|---|---|
| 400 | Copy links not allowed for support file | The copyLinks parameter is only applicable for main files and cannot be used with support files. |
| Status | Detail | Description |
|---|---|---|
| 400 | Resources cannot be provided for a support file | The resources field is only valid for main files during package uploads. Support files cannot have their own resources attached. |