Troubleshooting the Boomi Files.com Partner Connector

If your process stops on an application error or passes an error response to a later step, check the operation's Return Application Error Responses setting. Confirm that the process uses a connector version that supports the setting.

Inspect the returned error response or Process Reporting to identify the failure before changing credentials or file paths. For a List action, confirm that the operation succeeded before treating a result with no items as an empty folder.

Invalid API Key

Invalid or revoked API Keys produce the following error:

[401] The API key or Session token provided could not be used to validate this request.

Update the connector with a valid API Key and retry the process.

Not Found

When the file or folder path does not exist on Files.com, or the API Key does not have permission to access it, the operation produces the following error:

[404] Not Found.  This may be related to your permissions.

Files.com returns this error for both causes.

Confirm that the path exists on Files.com. Before attempting a download, confirm that the file exists by running the List action against the folder that contains it. To explore the available folder structure, start your List operation at /, the root folder.

Confirm that the API Key has permission to access the path on Files.com, or switch to an API Key that does. A site-wide API Key has access to all folders, but a path that does not exist still produces this error. If the API Key is owned by a user account, confirm that the user account has access permissions to the path.