You are here:
MDP Troubleshoot API Data Streams
Errors can occur that prevent API data streams from being created or processed. For example, it’s possible you used invalid credentials and processing failed. You can view errors using the Log button. The log contains important technical information and can help you diagnose issues.
The log for API Connections doesn’t store individual files, but each line of the log analyzes each time the API was called to process a given set of dates. The same technical information used to determine why the call failed is available via the Show More option.
Here are some common errors that occur and possible solutions:
Error: INVALID_CREDENTIALS "Invalid Credentials"
Credentials are the security tokens most APIs use to authenticate access to the source systems. Two scenarios can cause the Invalid Credentials error:
- The security token is expired and requires re-authentication.
- The credentials have changed password values.
Possible Solution:
The fix is the same for both scenarios.
- Navigate to the Import tab.
- Click Data Source Authentication.
- Select the credentials that are being used in the failed API stream, and click Refresh Token, and then enter your credentials.
Error: ‘Provider Internal Error’
As the name indicates, this is an error on the provider’s side. This error can be due to any number of reasons.
Possible Solution:
Because this is a provider error, MDP support can’t do anything to resolve the issue. Typically, waiting a few minutes and processing the data stream’s failed date ranges resolves the issue. Sometimes you see some dates process successfully and other dates fail again. In this case, wait an additional 5–10 minutes, and then process the remaining failed days.
Error: Security Error: invalid value "...path may contain malicious code"
This error occurs when a page path is identified as code and blocked for security reasons.
Possible Solution:
Because this isn’t malicious code, you can prevent it from being blocked by using this
formula: STRIP_HTML(csv['page_path']).
After applying the formula, reprocess the failed days.
Error: FORMULA_EVALUATION_FAILED "Formula evaluation failed"
This error occurs when a formula applied to the data stream can’t run on all the data it’s applied to.
Possible Solution:
Edit the formula, and try reprocessing the data stream again.
Error: Workspace/Account rows quota reached
When a workspace or account exceeds its total rows limit, data streams can’t process and fail. Every account has a limited number of rows according tou your license agreement. This number is divided between the account's workspaces. The error in question appears when either the account or one of its workspaces has reached their row limit.
When an account reaches its row limit, 'Account rows quota reached' error appears.
When a workspace reaches its row limit, 'Workspace rows quota reached' appears.
Confirm the Error:
- Users can track the row usage from the account or workspace settings under Data Row Usage.
Possible Solution:
- Contact your Salesforce representative.
Error: INVALID_DATE_RANGE "Invalid date range"
This error occurs when the date range of a file includes a large number of years. The platform recognizes that the date range is unreasonable and doesn’t upload the file. Sometimes a wide date range is the result of a problem with the date format. When this error occurs, it’s advisable to check the date format in the failed data streams.
- Only dates within 15 years of the current year can be processed. Anything beyond this period results in the data stream failing with the “Invalid date range” error.
- Fifteen jobs can be processed simultaneously per workspace. All other jobs starting at the same time are added to a queue and set to Pending until processed.
