Common Errors in HubSpot

this article covers the common errors you might encounter in hubspot, along with their possible reasons and troubleshooting steps these are simple troubleshooting steps; if you encounter difficulties or the problem persists, feel free to contact us for further assistance 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 docid\ ccoxsewhgmnnbs6gcv6h2 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 https //app cloudfiles io/ 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 docid 9ibd0tgbyrtn kgjpxhtn 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 true 150,241 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type important note on integration users 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 true 150,241 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type important note on integration users 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 docid\ wqal9oeb5 ei8hsg1zckm 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