Skip to main content
Skip table of contents

How To Handle Common Types of Actions Issues


Understanding and dealing with issues in Actions can sometimes be difficult, so use the below table for helpful tips on how to address some common types of issues. For instructions on how to find errors/see specific errors, review the How To QA Your Action Runs documentation.

Note: All IDs or names present in any photos are fake and obscured in many cases.

Clarification on Errors vs. Non-Errors:

  • Errors: When the tool encounters an issue or limitation during processing, it generates a clear error message. These errors signify a problem with the tool's functionality or operation and require troubleshooting to resolve.

  • Data Availability Issues (Non Errors): It's important to understand that the tool operates based on the data available to it. If there's no data present in the designated source (e.g., Google Sheet, Alli Data report), the tool cannot execute actions. You can identify a non-error scenario when an action completes successfully with 0/0 items sent, accompanied by an audit message stating "deployment complete: no items found."


Responsibility Clarification:

  • When an action doesn't occur due to lack of data, it's not an error with Alli Actions. Rather, it indicates an issue with the data availability or configuration.

  • Troubleshooting in such cases should focus on identifying why the expected data wasn't passed to the tool. Common reasons include filters applied in the Alli Data report, data not loading into the designated Alli Data datasource, or missing/filtered data in Google Sheets.

This documentation includes instructions for addressing both error and non-error scenarios.

Common Errors

If you see one of these errors, follow the recommendations. If you do not see your specific action or are unable to remedy the issue with the information provided, reach out and create a ticket for further assistance

Error Type


Explanation / Recommendation

Missing Required Columns

Missing columns required by "[Action Name]" (#931afa02-5d6d-4292-a6a9-bbb1e5a88175): "customer_id", "keywordtext", "keywordmatchtype", "campaign_resource_name"


The Action requires specific columns (in the example, "customer_id", "keywordtext", "keywordmatchtype", "campaign_resource_name". They can be found at the Set Datasource stage.

Review your datasource to ensure:

  1. You have each of the columns specified and are not missing any

  2. They match the column names listed and expected (Keyword Text Value vs keywordtext, for example)

Undefined Table (Datasource or Report not found)

An exception occurred while executing a query: SQLSTATE[42P01]: Undefined table: 7 ERROR: relation "[CLIENT_NAME.REPORT_NAME]" does not exist


You have likely selected an Alli Data report or datasource as the datasource for your Action. Review your report/datasoruce and ensure

  1. Your report is published (see Getting Started with Explorer Reports for instructions on how to publish

  2. Your datasource is active and contains data (if you’ve newly created it for your action, ensure there is data)

Invalid ID

Example of Scientific Notation

InvalidArgumentException(code="0"): Object ID must be an integer or integer string but was passed "1.61573E+12" (string). Please use an integer string to prevent integer overflow.


Example of Rounding (in Meta) on ID

GraphMethodException(httpStatus=400, code=100, subcode=33, trace=AqnMnSUTb5dZP0FHvgurWB-): Unsupported post request. Object with ID '238442406440580' does not exist, cannot be loaded due to missing permissions, or does not support this operation. Please read the Graph API documentation at `

The error may look different for each platform, but ensure your IDs are being passed as strings, not as numbers, as systems (like Alli Data, Google Sheets, etc) sometimes change the format of numbers by either rounding or utilizing scientific notation

  • IDs very rarely end in 0 so double check for rounding instances where you are confident you gave the right ID, but the error says it does not exist or is invalid

Expired Token/Authentication

Meta Example: AuthorizationException(httpStatus=400, code=190, subcode=460, trace=ANGu1DZ3eJu6tHx85Ai0lPF): Error validating access token: The session has been invalidated because the user changed their password or Facebook has changed the session for security reasons.

Reference the How Manage Partner Platform Authentication in Actions documentation for instructions on how to refresh or replace the authentication.

Data Availability Issues (Non Errors)

Sometimes, when you're counting on an Action to handle tasks in your accounts automatically, it can be a bit frustrating if nothing seems to happen. You might start wondering if the tool has hit a snag or isn't working properly. But here's the thing: often, the tool is doing its job just fine. The real hiccup is that the necessary data isn't there, ready, or accessible when the Action runs. So instead of blaming the tool outright, it's worth checking where the data is coming from in these situations.


Here's an example of a successful Action run that resulted in sending 0 items. While this might be perfectly normal in many cases, if you were expecting these actions to make changes in your account, it's a hint that there might be a data availability issue.

A few handy tips and tricks in this instance, along with relevant documentation:

Google Sheet Integration:

  • Documentation: How To Connect your Google Sheet to Actions

  • Tip: Review the history on the connected tab history to ensure data was present at the time the Action ran.

  • Tip: If using filters, review both the filter and the raw data to ensure proper data retrieval.

  • Tip: For filtering dates, check the time zone of your Google Sheet, Action schedule, and base data. Make necessary adjustments for data availability. The documentation linked above contains helpful guides, so refer to that.

Alli Data Datasource or Report:

  • Documentation: How To Filter Alli Data Reports by Date to Power Actions - Tips & Tricks

  • Tip: Review the audit page of your datasource for loading status and errors.

  • Tip: When using filters, ensure both filter settings and raw data are reviewed for accurate data retrieval.

  • Tip: Check documentation for proper handling of dates and time zones when filtering dates.

When in doubt, please always reach out to the team in #alli-actions or by submitting a ticket

If you're feeling uncertain about where to begin, take a look at this step-by-step walkthrough. In this video, we guide you through investigating a data availability non-error. You'll learn how to identify instances where the tool hasn't taken action due to a lack of data, and we'll show you practical steps to troubleshoot and resolve the issue.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.