We try really hard to prevent it, but errors are going to pop up. This can be because of existing properties or resources in the target portal, mismatch existing resources, permission issues, temporary delays, etc. So what do you do when you see an error.
In general, we recommend you try to install that failed resource again. It's safe to try again and see if the error still occurs. Sometimes, it will go away when you retry the install. (This happens because of temporary processing delays in HubSpot, or temporary internet issues when the package is installing.)
If the error still appears, try to read the text to see if anything stands out. Even though it looks technical, there's usually a sentence or phrase in the error that gives away the root cause.
If your error is not present on this list, please reach out to your PSM or Support so we can investigate further!
Common Errors:
Dependent Resource Not Found
Supered works by bringing over all the dependencies in an asset to ensure that it can work in the new receiving portal. If a dependency is not found, Supered will error out because the asset will not be able to function in the new receiving portal without it.
These errors will read, "XYZ Asset not found: (Name of Asset)"
To fix:
Re-add the asset that failed to the package.
When the dependency resolver pops up, add all dependencies.
It will not double-add dependencies if they already exist in the package.
2. If you do not have access to the original portal OR the asset no longer exists, you can create the missing dependency in the RECEIVING portal and re-install.
List Not Found
Lists can take a moment to process inside HubSpot, so you may receive an error that another asset has failed because of "List Not Found".
To fix:
Make sure the list is present in the package. If not, follow the steps from above to remedy.
Refresh the package and install the single resource.
Property Type Does Not Match
When adding properties to a new portal, Supered will search first to see if the internal name exists. If the internal name DOES exist, Supered will then look to see if the property types are the same.
If the property types are the same, Supered will then give you the option to add additional options from the source portal that are not present in the receiving portal (in case of multiple checkboxes, drop down, etc.)
If the property type is NOT the same, Supered will give you an error and continue installation. The error will tell you what the receiving portal has "Actual" versus what was in the source portal "Expected."
To fix:
You can either update the source portal property type to match receiving portal or update the receiving portal to match the source portal.
Please note, you can only do this if there is no data currently in the property.
You can also choose to ignore the error- resources that have this property will still deploy since the dependent property lives in the receiving portal.
"This app-cookie does not have proper permissions"
This error will prevent the creation of assets and will be found in the body of the error text. This means one of 2 things:
The user installing does not have permission to create certain assets.
The receiving HubSpot instance does not have the right permissions to create the assets.
For example, the package contains a Custom Object and the HubSpot receiving portal is a Starter, not Enterprise.
To fix:
Update the User permissions, if applicable. The error will tell you what specific permissions are missing.
In this example, the User did not have the ability to create new properties.
Upgrade the receiving portal so they can have the cool functionality you are building 😊.