Troubleshooting
Troubleshooting Errors in the Command Credit HubSpot Integration
This article explains the most common errors you may encounter when using the Command Credit integration inside HubSpot, what they mean, and how to resolve them.
Errors are grouped by where they occur, so you can quickly find the relevant section and take action.
How errors work in this integration
Errors may appear when:
-
Running Business Search
-
Running the Risk Dashboard
-
Loading the integration card on a company record
Most errors are safe to retry and do not indicate data loss or misconfiguration.
If an error persists after retrying, it may require admin review or support assistance.
How to use this guide
For each error, you’ll see:
-
Error message – what you see in HubSpot
-
What it means – a plain-English explanation
-
Recommended action – what to do next
If you need to contact support, include:
-
The exact error message
-
A link to the affected company record
-
The approximate time the error occurred
Business Search errors
These errors occur when running Business Search, which identifies a company and retrieves baseline business information.
Common Business Search errors
| Error message | What it means | Recommended action |
|---|---|---|
| Missing required fields: | Required business details are missing (e.g. Business Name, Address, City, State, or Zip). | Fill in all required fields on the company record and try again. |
| Business search failed or no data returned | No matching business could be found using the provided details. | Double-check the business information and retry. |
| PPR search failed or no data returned | Additional company details (such as Tax ID or SIC Code) could not be retrieved. | Proceed without these fields or try again later. |
| RDash search failed or no data returned | Risk data could not be retrieved during the business search step. | Try again later or run the Risk Dashboard after search completes. |
| API request failed: | The external credit service could not be reached (timeout, credentials, or server error). | Retry after a short delay. If it persists, verify API credentials and connectivity. |
| HubSpot operation failed: | Business data was retrieved but could not be saved to HubSpot. | Retry. If it persists, check HubSpot permissions and logs. |
| Error running business search | A non-specific error occurred and no detailed cause was captured. | Retry. If it continues, review server logs. |
Risk Dashboard errors
These errors occur when running the Risk Dashboard, which requires a successful Business Search first.
Important dependency note
The Risk Dashboard cannot run without a BIN (Business Identification Number).
The BIN is only created after a successful Business Search.
Common Risk Dashboard errors
| Error message | What it means | Recommended action |
|---|---|---|
| Please run Business Search first to obtain BIN. | A risk check requires a BIN, which does not yet exist. | Run Business Search successfully, then run Risk Dashboard. |
| BIN is required to run Risk Dashboard | The backend did not receive a BIN. | Ensure Business Search completed successfully and retry. |
| Company ID is required | The system does not know which HubSpot company to update. | Ensure the integration card is opened on a company record and retry. |
| RDash search failed or no data returned | No risk data was returned by the external service. | Retry later or verify the BIN is correct. |
| HubSpot operation failed: | Risk data was retrieved but could not be saved to HubSpot. | Retry. If persistent, check HubSpot permissions and logs. |
| No data returned from Risk Dashboard | The request succeeded but returned an empty response. | Retry later. If it persists, inspect server logs. |
| Error running Risk Dashboard | A non-specific error occurred during the risk check. | Retry. If it continues, check server logs. |
General & loading errors
These errors are not specific to Business Search or Risk Dashboard and usually relate to record context, permissions, or temporary system issues.
Common general errors
| Error message | What it means | Recommended action |
|---|---|---|
| Company ID not found in context | The integration card did not receive a company ID when loading. | Reload the record and ensure the card is placed on a company record. |
| Missing companyId parameter | A backend function was called without a company ID. | Ensure the current company ID is passed when invoking the function. |
| Error loading data | A non-specific issue occurred while fetching initial data. | Refresh the page and try again. |
| Internal Server Error | The server encountered an unexpected issue. | Try again later. If it persists, check server logs. |
| An unexpected error occurred | A fallback error when no specific cause is available. | Retry. If it persists, collect logs and contact support. |
Understanding placeholders in error messages
Some error messages include placeholders:
-
Replaced with a comma-separated list of missing required fields (e.g. Name, Address). -
Contains raw error details from HubSpot or the external API.
This information is useful for support but is not required for most retries.
When should I contact support?
Contact support if:
-
The same error occurs repeatedly after retrying
-
Credit or risk data is retrieved but never saved to HubSpot
-
Errors occur across multiple company records
When contacting support, include:
-
The exact error message
-
A link to the affected company record
-
The approximate time the error occurred