The article is divided into two sections: Workflow Errors and File Viewer Errors. You can check out specific errors by navigating from the Table of Contents.
Common Workflow Errors
This section covers various workflow-related errors that you might encounter.
1 - "Library not connected"
This is the most frequently encountered error and usually occurs when your cloud drive library isn't connected to CloudFiles. To resolve this issue, start by opening the CloudFiles app in HubSpot. Next, connect an automation user. These steps have been exmplained in details below -
Access the CloudFiles App in HubSpot
Log in to your HubSpot account using your admin email. Navigate to any contact, company, or deal record. Find the CloudFiles widget on the right side. At the bottom of the widget, click the CloudFiles link, then select "Go To CloudFiles" in the dialog box to open the app dashboard. Check out How to go to the CloudFiles App Dashboard? for more detailed steps.
Refer to the GIF below to have a visual understanding of these steps -
Connect an Automation User
To link your automation user to cloud drives like SharePoint or Google Drive, log into the CloudFiles dashboard at CloudFiles. Go to Settings > Integrations > Cloud Library. Choose your desired cloud library and click 'Connect' at the top right. Complete the authentication process, and the library will show as 'Connected'. Check out What is an 'Automation User' and how does it work? for more detailed steps.
Refer to the GIF below to have a visual understanding of these steps -
If you continue to encounter difficulties or if the problem persists, please feel free to contact us for further assistance.
2 - "Destination Not Found"
This error often occurs due to incorrect folder names/paths, formatting issues, or permission problems. To resolve these issues, please refer to the respective solutions below -
| Reason | Resolution | |
|---|---|---|
| Incorrect Folder Name or Path | The folder name and the path given might be wrong. | Ensure the folder name is correct. Verify that the entire path is correct. Manually navigate to the location to ensure it exists, and accurately copy the path from the metadata |
| Formatting Issues | There could be a problem with formatting the path or the folder name. For instance, if there's an unnecessary slash or space in the path or folder name. | Make sure there are no extra slashes (/) or leading and trailing spaces in the path or the folder or record name. |
| Permission Issues | The automation user doesn’t have direct access to the folder. | Ensure the automation user has the necessary permissions to access the folder. |
| Automation User Issues | At times, the automation user connection in the CloudFiles Dashboard may become stale. | Reconnect your automation user for Cloud Drives. See this article for a detailed step-by-step walkthrough. What is an 'Automation User' and how does it work? |
In some cases, the “Destination Not Found” error may occur even when the folder or library appears visible to the user in the CloudFiles content library. This typically happens when the integration user is different from the user currently browsing the library.
For example, if the integration is set up with ramona@gmail.com but tom@gmail.com connects a document library during setup, Tom may be able to see all sites and folders in the interface. However, when CloudFiles automation is triggered, it will execute under Ramona’s credentials, not Tom’s. If Tom does not have access to the destination, the automation will fail and throw the “Destination Not Found” error, even though everything appears connected.
✅ To avoid this: Always ensure that the user who connects the storage (via CloudFiles) and the user executing automations are the same, or that the integration user has explicit access to the required folders or libraries.
If you continue to encounter difficulties or if the problem persists, please feel free to contact us for further assistance.
3 - "Resource Not Found"
This error occurs with any CloudFiles flow action that involves a path. Here are the common reasons and their respective solutions -
| Reason | Resolution | |
|---|---|---|
| Incorrect Path or Drive ID | The path or Drive ID provided is incorrect. | Navigate to the specified path manually in your cloud storage to confirm it’s correct. Copy it correctly from the metadata. |
| Deleted Resource | The folder or file you are trying to access might have been deleted. | Make sure the folder or file you’re trying to access still exists and hasn't been moved or deleted. Update the flow if the resource has changed location or needs to be replaced with a new one. |
| Permission Issues | The integration user doesn’t have access to the resource | Log into your cloud storage and check the permissions for the folder or file. Grant the necessary permissions to the integration user. |
In some cases, the “Resource Not Found” error may occur even when the folder or library appears visible to the user in the CloudFiles Content library. This typically happens when the integration user is different from the user currently browsing the library.
For example, if the integration is set up with ramona@gmail.com but tom@gmail.com connects a document library during setup, Tom may be able to see all sites and folders in the interface. However, when automation is triggered, it will execute under Ramona’s credentials, not Tom’s. If Tom does not have access to the resource, the automation will fail and throw the “Resource Not Found” error, even though everything appears connected.
✅ To avoid this: Always ensure that the user who connects the storage (via CloudFiles) and the user executing automations are the same, or that the integration user has explicit access to the required folders or libraries.
If you continue to encounter difficulties or if the problem persists, please feel free to contact us for further assistance.
4 - "Invalid Input"
This error often occurs with the Create Attachment Action flow action. It mostly occurs due to -
- Library Not Connected: The cloud drive library isn't connected.
- Incorrect Root Folder ID or Path: The root folder ID or the path given is incorrect.
- Wrong Folder Name or Formatting: The folder name is misspelled or formatted incorrectly.
Make sure your library is connected and accurately enter the folder name, root folder ID, and path in the flow action settings to avoid errors. If you continue to encounter difficulties or if the problem persists, please feel free to contact us for further assistance.
5 - Unauthorised Error
This type of error occurs when your CloudFiles plan expires. You can upgrade your plan by contacting us.
6 - Internal Server Error
For internal server errors, please contact us.
Common File Viewer Errors
This section covers various File viewer-related errors that you might encounter.
1 - “Sorry, we can't find the file you are looking for”
This error occurs immediately after creating a new link for a document because the system is fetching and converting the file from external storage to display in the viewer. You may need to wait a few seconds for the slides to appear. This delay only happens the first time you create the link; it will work consistently afterward.
Common Widget Errors
This section covers various widget-related errors that you might encounter -
1 - "Application error: a client-side exception has occurred..."
For this application error, please contact us.