Monitor workflows

Sending data from Amperity is a combination of three things: building a query, linking the results of that query to an orchestration that sends the results to a destination, and then monitoring the workflow to ensure that your data safely makes it downstream.

This is part three of a series of topics that describes how this works.

  • Build queries using Presto SQL. A SELECT statement, along with standard clauses, operators, and functions, is all you need to return data that support any use case.

  • An orchestration connects the results of your query to a workflow that sends those results to its destination.

  • A workflow manages the process of sending that data to the selected destination.


    Each workflow is monitored by Amperity. You may see notifications about the state of the workflow within the Queries and Destinations pages. Depending on the type of notification, you may be directed to a workflow actions page that will actively help you troubleshoot issues within that workflow.

You can view workflows from the Workflows page, from which you configure the audience and sub-audiences that will be associated with the campaign, the downstream locations to which the campaign will be sent, and the time at which the campaign is to begin.

The following sections describe what you should do to monitor the health of each query result that you send downstream from Amperity.

Step 1.

Ensure that each query results match the requirements and/or use case(s) that are required in the downstream application.

For example, you may need to update a query to match changes required by the destination. This might be due to a change in the scope of the use case, such as a request to add columns to the “Yearly_Revenue_by_Month” query to support an additional visualization element in your Domo dashboard.

You may need to update a query to ensure the results match specific requirements by the destination.

For example, you started with 6 data sources and used those to get your downstream use cases running. And then added a few more data sources. One of these sources has “messy records” that changed some of the data in your customer 360 database, which causes your Google Ads or DV360 orchestration to fail. Google Ads or DV360 requires phone numbers to use a “+11231234567” format and requires that first name, last name, zip code, and country be available to the the “Contact Info” upload key. An orchestration will fail when the data that is sent to Google Ads or DV360 doesn’t match the formatting requirements.

Step 2.

Ensure that all of your orchestrations are running successfully. You can monitor this from the Workflows page.

Some workflows may have errors that will prevent the workflow from completing successfully. Use the Workflows page to resolve workflows that failed by reviewing options for resolution, and then choosing one of those options or choosing to restart the workflow.

The Workflow page, showing a workflow with errors.

When you discover an orchestration that has failed, open workflow actions:

  1. From the    menu in the top navigation bar select Workflow. This opens the Workflows page.

  2. Select a workflow with a “ Failed” status.

  3. Click Show Resolutions, review your options, and then select a resolution. Work through any steps that may be required by the selected resolution.

  4. Click Resolve.

Step 3.

Troubleshoot orchestration failures caused by incorrect settings in Amperity or in the downstream system.

For example, the name of a data extension must be unique within Salesforce Marketing Cloud, should use underscores ( _ ) instead of spaces, and may not contain any of the following characters:

! @ # $ % ^ * ( ) = { } [ ] \ . < > / " : ? | , &

The name of the data extension is configured in the data template, which means you can troubleshoot this type of failure directly.

Step 4.

Notifications show a status for individual steps within workflows that are related to queries and orchestrations. The status can be “Running”, “Completed”, “Alert”, and “Error”.


All notifications within your tenant are specific to your tenant and reflect how your tenant is configured. The names of tables, databases, queries, orchestrations, and destinations will appear in the notifications.

If there is an error, such as a processing error related to a specific column within a custom table, the notification will contain the names you used for that custom table and also for the columns within that table.

A warning is shown when the workfow was able to complete all steps, but detected issues with at least one step within the workflow.

An error is shown when the workfow was unable to complete all steps.

A notification will describe the issues related to warnings and errors, with specific information about what caused them. For errors, you should open the Workflows page and review the error. A list of suggested workflow actions will be available.


If you are unable to resolve an error, please contact Amperity support.