404 Error: "Something went wrong"

what is the issue? salesforce flows using cloudfiles actions might fail and produce the following generic error sometimes an apex error occurred cldfs cloudfilesexception {"statuscode" 404, "message" "something went wrong"} this usually indicates that the salesforce flow attempted to access a resource (such as a file or folder) that doesn’t exist or isn't accessible in the connected external storage why does this happen? the 404 "something went wrong" error can occur when cloudfiles cannot locate the specified file or folder in the external storage due to a few reasons an incorrect file name or folder path the resource was deleted or moved from external storage the integration user lacking required permissions to the resource misconfiguration in the salesforce record causing a missing link to a parent folder this error doesn't indicate a bug in cloudfiles but rather a misconfiguration or issue with the specified resource path or permissions 1 an incorrect file name or folder path what is the issue? formulas used in salesforce flows to dynamically build paths (for example, parentfolderpath + "/subfolder" or folderpath + "/filename ext" ) are sensitive to case, spelling, and character accuracy even minor discrepancies—such as incorrect casing, missing characters, or typos—can cause cloudfiles to attempt accessing resources that don't exist in the external storage, resulting in a 404 error this issue frequently arises when names are manually entered into flow formulas or copy pasted incorrectly when this occurs the resolved path from your formula does not match any actual file or folder in your external storage cloudfiles throws a 404 error because it cannot locate the specified resource example scenario in one instance, a user created a flow formula to resolve the path to a folder called new setup documents , but accidentally wrote new setup docs because the actual folder in external storage is named "new setup documents", cloudfiles attempts to access the incorrect path (new setup docs), fails to locate the resource, and returns a 404 error how to fix this issue review and correct the folder or file names within your salesforce flow formulas ensure an exact match—including casing, spelling, and special characters—to the corresponding names in your external storage once corrected and redeployed, cloudfiles will successfully locate the intended resource, resolving the 404 error 2 the resource was deleted or moved from external storage what is the issue? another common reason for the 404 error is when a file or folder connected to a salesforce record has been moved, deleted, or renamed in the external storage (e g , sharepoint, dropbox) this causes the existing path reference stored in salesforce to become invalid when this occurs salesforce continues to reference the old, now non existent resource path cloudfiles tries to access or interact with this resource, which no longer exists at that location a 404 error is returned from the external storage provider's api this issue can be difficult to identify unless you have monitoring or regular checks in place to ensure that referenced resources still exist example scenario in one case, a flow attempted to run a document related action on a previously connected account folder however, the folder had been deleted from sharepoint by another user, thereby breaking the linkage between salesforce and sharepoint that cloudfiles relies upon as a result the flow attempted to access a folder that no longer existed sharepoint responded with a 404 error, indicating the resource couldn't be found salesforce didn't display any visible errors; instead, the flow silently failed how to fix this issue verify that the referenced file or folder still exists in your external storage if deleted, either recreate or restore the missing resource reconnect the file or folder to salesforce using the cloudfiles widget to refresh the path reference once the connection is restored, cloudfiles actions will function correctly, and the 404 error will be resolved 3 the integration user lacking required permissions to the resource what is the issue? a 404 error may occur when the integration user configured in the cloudfiles app doesn’t have access to a specific file or folder in the connected external storage (e g , sharepoint, google drive, dropbox) this user is set under document management > libraries in the cloudfiles app and is responsible for performing actions like retrieving files and folders during flow execution if this user lacks the necessary permissions, the storage provider responds with a 404 error — not because the resource is missing, but because it’s inaccessible to the integration user when this occurs the salesforce flow attempts to access a file or folder via cloudfiles the integration user tied to the external library doesn’t have permission to view or retrieve that resource the storage provider treats the resource as “not found” and returns a 404 error this often leads to confusion, as it appears the resource is missing, when in fact the issue lies in permission settings example scenario at a firm using cloudfiles with sharepoint, a salesforce flow failed with a 404 error while trying to access a project subfolder the integration user had access to the main site but lacked permissions on that specific subfolder due to custom folder level restrictions once the user was granted proper access to the folder, the flow executed without errors how to fix this issue open cloudfiles app > document management > libraries and check which user is set as the integration user for the affected library in the external storage system, verify that this user has appropriate access (typically read or read/write) to all relevant files and folders update the user’s permissions if necessary to ensure visibility and access to the resource once access is granted, re run the flow or action to confirm the error is resolved 4 misconfiguration in the salesforce record causing a missing link to a parent folder what is the issue? another potential cause of the 404 error is a misconfigured folder connection in salesforce in most cases, cloudfiles flows expect a salesforce record to be linked to a parent folder in the external storage from there, the system programmatically accesses subfolders as needed however, if a user mistakenly connects a subfolder directly to the record — instead of the expected parent folder — cloudfiles will attempt to retrieve a subfolder that doesn’t exist, resulting in a 404 error when this occurs a flow attempts to retrieve a specific subfolder relative to the folder connected to the salesforce record since that nested structure doesn't exist, the external storage provider returns a 404 error example scenario in one case, a job record was mistakenly linked to the “working files” subfolder instead of its parent job folder when the flow attempted to retrieve the “working files” subfolder, it effectively searched for a path like /working files/working files , which did not exist this caused the “get folder details” action to fail, and a 404 error was returned by the external storage api how to fix this issue ensure that the correct parent folder is linked to the salesforce record avoid manually connecting subfolders unless explicitly required by your logic use the disconnect / connect folder option in the cloudfiles widget to reset and relink the folder properly after updating the folder connection, re run or debug your flow to confirm that the 404 error is resolved