Troubleshoot API Data Streams in Marketing Cloud Intelligence

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.

1. Navigate to the Connect & Mix tab.
2. Expand Data Streams, and then click Data Source Authentication.
3. 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, Marketing Cloud Intelligence 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: The workspace exceeded total rows or The Account exceeded total rows

Every account has a limit to the amount of rows it can use. This amount is divided between the account’s workspaces. The error in question appears when the account or one of its workspaces reaches its row limit. When the account reaches its row limit first, the ”The account exceeded total rows” error appears. When the workspace reaches its row limit first, the ”The workspace exceeded total rows” appears. After a row limit is reached, data streams fail and data isn’t uploaded to the workspace or account. Admins can track the row usage under the Settings menu in the Account/Workspace Usage Data section.

Possible Solutions:

• Delete data from the workspace using the delete data feature. Changes can take up to 30 minutes to apply.
• To increase the account/workspace’s row limit, contact your Account Manager. Changes in the row limit can take up to 30 minutes to apply.

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.

Error: Rate Limit Exceeded

This error occurs when the rate limits defined on the API provider's side are exceeded. Please note that this is a limitation on the provider's end and the Marketing Cloud Intelligence support team can’t do much to overcome this error.

Rate Limits are defined on the provider's side and vary from API to API - every API has different limitations. In addition to this, the limitation might be specific to your credentials that are linked to the provider in question.

They can also vary in type - for example, there might be a Daily Limit on how many requests your account can make to the provider for a given day. The provider may limit the number of requests from a specific account, so it only allows a few to pass successfully while others are rejected due to Rate Limits.

These limitations may be related to the specific credentials used to access the Provider's Database (the credentials used inside the API stream).

Possible Solution

It’s recommended you wait a day, and then process the data streams with failed jobs the next day. Rate limits are typically reset each day.