About workflows

Use the Workflow page to view the status of all tenant workflows, including:

• Who started it?

• How long it has been running?

• Is it an SLA workflow?

Note

The Workflows page is available to users of Amperity who are assigned the Amp360 User policy or the DataGrid Operator policy. The Workflows page is not available to users who are only assigned the AmpIQ User policy.

Workflow resolution types

Workflow resolutions are available to automatic and/or manual workflows for the following components:

Component	Automatic?	Manual?
Campaigns
Courier groups
Couriers
Data ingest
Database refresh
Orchestration groups
Orchestration

Workflows page

For each workflow you can view details about each individual task that was run, if any were skipped, and if any failed. The workflow tab automatically refreshes every 30 seconds and updates the status of any workflow that is currently in-progress.

You may filter down the list of workflows using the filters on the right side of the page.

Click the name of any workflow to open a page that shows the sequence of the workflow along with a list of each individual task and subtask.

The Workflow tab can be accessed by administrators and DataGrid operators and is available from the ellipses menu in the top navigation.

Workflow alerts

Workflow alerts are sent when something happens to a workflow that requires customer intervention. Workflow alerts contain a description of the error that caused the workflow to fail, and a link to the workflow within Amperity. Once you access the workflow within Amperity, there will be a workflow resolution available to resolve the workflow failure and retry the workflow.

Workflow alerts can be sent as an email from notifications@amperity.com. If you reply to the email, the workflow alert will reply to support@amperity.com, and then will automatically open a support ticket.

Workflow alerts can also be sent through Slack.

You can opt in to receive workflow alerts using the Configure Alerts button at the top of the Workflows page. This opens a dialog box from which you can specify the audiences to which workflow alerts should be sent. Alerts can be configured by workflow type. To add an email address, type the full email address, i.e. “justinc@acme.com”, hit enter (or return) to add the email to the drop-down list, and then click Save. See Slack below for Slack integration details.

Workflow alerts are only sent for parent tenants. Alerting in sandboxes is not currently supported.

Courier groups

Alerts are sent when a a courier group workflow fails for a user-addressable reason. The scope of courier group workflow failure alerts include errors in credentials, connectors, feeds, data ingestion, custom domain tables, Stitch, or database generation. You can configure who receives alerts for courier group failures by editing the audiences under “Courier Groups” in the workflow alerting dialog.

Courier group failure alerts are sent for courier groups that are run manually or on a schedule, and include both SLA and non-SLA courier groups.

Some examples of courier group failure alerts include (but are not limited to):

Sources:

• Failed to connect errors across different connectors

• Credential not found

• SFTP failures

• Empty ingest failures

• PGP decryption errors

• Missing feeds or differing feed schemas

• Empty custom domain tables

Stitch:

• Stitch jitter alerts

Database generation:

• Errors resolving column names in tables

• Missing tables

Note

Alerts are also sent when a courier group workflow run as SLA has detected that it is missing files.

Missing file alerts include:

Workflow paused - missing required files

The courier group has detected missing files that are specified as required to run, so the courier group has been paused. This pause is in addition to any wait times already specified for couriers in the courier group.

The courier group will automatically wait an additional 5 hours for required files to appear before failing.

Workflow paused - missing required and optional files

The courier group has detected that it is missing files that are specified as required and optional to run, so the courier group has been paused. This pause is in addition to any wait times already specified for couriers in the courier group.

The courier group will automatically wait an additional 5 hours for required files to appear before failing. If only optional files are available, the courier group will fail. If only required files are available, the courier group will continue running without optional files.

Workflow continuing - found required files

The courier group that was previously paused to wait for missing required files has found those files and is running.

Workflow failed - missing required files

The courier group has waited an additional 5 hours beyond the original start time and any wait times specified, but is unable to locate required files to begin the workflow. The workflow has failed, but can be retried with a workflow resolution.

Workflow failed - missing required and optional files

The courier group has waited an additional 5 hours beyond the original start time and any wait times specified, but is unable to locate required files to begin the workflow. Optional files are also missing. The workflow has failed, but can be retried with a workflow resolution.

Workflow continuing - missing optional files

The courier group has located any missing required files and is continuing the workflow without missing optional files.

Orchestration groups

Alerts are also sent when an orchestration group workflow fails. The scope of orchestration group workflow failure alerts include errors in queries that power orchestrations as well as the orchestrations themselves. You can configure who receives alerts for orchestration group failures by editing the audiences under “Orchestration Groups” in the workflow alerting dialog.

Orchestration group failure alerts are sent for orchestration groups that are run manually or on a schedule, and include both SLA and non-SLA orchestration groups.

Campaigns

Alerts will be sent for failures that happen when sending a campaign or building the campaign audience. You can configure who receives campaign failure alerts by configuring the audiences in the “Campaigns” text box in the workflow alerting dialog.

Column name cannot be resolved

Amperity must be able to find the column from which campaign attributes will be pulled before sending them to your destinations. If a column is renamed or removed the campaign will fail, you will receive an error message, and an alert will be sent.

To resolve this error, open the link in the alert and visit the workflow actions page. The alert and workflow actions page will both contain the error message, which will be similar to:

SYNTAX_ERROR: Column <column name> cannot be resolved

or:

COLUMN_NOT_FOUND: Column '<column name>' cannot be resolved

Follow the steps in the workflow action to identify which column is causing the error, and then work with your DataGrid Operator to fix the column name that cannot be resolved.

Mismatched datatype

A datatype defines what the value of an attribute can be. For example, an email address is a String, an order date is a Datetime, revenue is a Decimal, the number of items in an order is an Integer, and something that can be true or false is a Boolean.

It’s possible for datatypes to be mismatched, which occurs when a campaign expects a datatype to be a String, but is returned as a Decimal (or some other non-String datatype). If a mismatched datatype occurs the campaign will fail, you will receive an error message, and an alert will be sent.

To resolve this error, open the link in the alert and visit the workflow actions page. The alert and workflow actions page will both contain the error message, which will be similar to:

SYNTAX_ERROR: '=' cannot be applied to varchar, integer

Follow the steps in the workflow action to identify which table is causing the error and then either update the campaign to select attributes from a different table or work with your DataGrid Operator to fix the table.

Missing table

Amperity must be able to find the table from which campaign attributes will be pulled before sending them to your destinations. If a table is renamed or removed the campaign will fail, you will receive an error message, and an email will be sent.

To resolve this error, open the link in the alert and visit the workflow actions page. The alert and workflow actions page will both contain the error message, which will be similar to:

Cannot select data from missing tables: <table name>

Follow the steps in the workflow action to identify which table is causing the error and then either update the campaign to select attributes from a different table or work with your DataGrid Operator to fix the table.

Slack integration

You may integrate Amperity with your Slack workspace to receive workflow alerts. This lets you send alerts about your workflows to Slack channels or Slack users, providing an alternative to email as a destination to receive alerts.

Like email alerts, Slack alerts will contain details about the workflow failure as well as a link to the Workflow page with more details and a workflow resolution. You may only have one Slack workspace configured at a time.

Note

You may remove a configured Slack workspace by visiting the Credentials page and deleting the relevant Slack credentials.

Integrate with Slack

You can integrate with Slack to receive workflow alerts.

To integrate with Slack

1. From the Users & Activity page, in the Slack Integration section, click Add Slack Integration.

   Note

   You will need to be assigned to the User Administrator policy option to see the Users & Activity page.

2. On the Configure Slack window, click Confirm.

3. Follow the steps to allow the Amperity app access to your Slack workspace.

Configure Slack alerts

Once you have added a Slack integration to your Amperity tenant you can configure how you receive alerts.

To configure Slack alerts

1. From the Workflows page, click Configure Alerts in the upper-right corner.

2. In the Configure Alerts dialog, find the Slack input for each alert category you want to be notified on, then input the name of each Slack channel from your workspace that you’d like to be notified.

   Note

   Every channel name you input must be prefixed with a # (e.g. #amperity-alerts)

Resolve workflow errors

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

To resolve workflow errors

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

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

3. Click Show Resolutions, review your options, and then select a resolution.

4. Click Resolve.

Resolution categories

The list of options you are provided to resolve workflow failures depends on the type of workflow, but fall into one of the following broad categories:

1. Retry task

2. Restart workflow

3. Context-specific resolution

A list of options is available for any failed workflow. To view the list of options, open the failed workflow, and then click Show Resolutions. A page opens that describes the error, and then provides a list of options.

Retry task

You can retry a task in the workflow. This resolution will re-run the workflow from the same failed task using the same inputs as those provided to the failed workflow.

Restart workflow

You can restart a workflow. This resolution will rerun the workflow from the same failed task against the current state of your tenant, taking into account any configuration changes you may have made.

Context-specific resolution

Some resolutions offer a fix specific to an area of the product, and will only show up in the list of resolutions if available. An example of this is retrying Stitch and allowing empty tables for the next run, if there was a failure in Stitch.

Some of these resolutions will also contain an extra step to allow you to change an input that applies to the next run, letting you quickly adjust a configuration parameter to get the workflow running again.

Because these only change an input for the next run, you will need to ensure that you make the same configuration change to the original part of the product if you want to persist the change going forward. An example of this is retrying Ingest with a new error threshold.

Available resolution types

Resolution type	Area	Description
Restart workflow	Data sources, Stitch, Customer 360, Campaigns, Orchestrations	This resolution allows you to restart a workflow after making a configuration change to your tenant. For example, by updating the credentials for a courier or by updating a query. Use this to make configuration changes, and then rerun a workflow that takes into account that configuration change.
Retry ingest with new error threshold	Data sources	This resolution allows you to increase error thresholds as a one-time exception, and then continue a workflow. Use this when your feed ingest fails because the errors in the feed have exceeded the configured threshold.
Retry Stitch with empty tables	Stitch	This resolution allows Stitch to run once with empty input tables, and then continue a workflow. Use this when a Stitch input table is empty, but you still want Stitch and the rest of your workflow to run.
Retry task	Data sources, Stitch, Customer 360, Campaigns, Orchestrations	This resolution allows you to retry tasks that have encountered transient errors while running.
Skip a feed	Data sources	This resolution allows you to select which feed(s) to skip, and then continue a workflow. Use this when a file with potentially malformed content is present in a feed, but you want that feed to be skipped for this workflow run.
Skip a courier	Data sources	This resolution allows you to skip a courier that failed while pulling data (e.g. deleted table, changed view, transient error with data source) and continue running the rest of the workflow.
Update credential	Data sources, Campaigns, Orchestrations	This resolution directs you to the credentials page to fix a broken credential (deleted, unauthorized, expired, etc), and then allows you to retry the workflow by clicking Resolve.
SFTP failure	Data sources, Campaigns, Orchestrations	This resolution appears if Amperity could not connect to the SFTP server. This might be because the server isn’t available, or the server is out of disk space. Troubleshoot the server and click Resolve to retry the workflow.
Corrupted archive	Data sources	This resolution option appears when a file you are trying to bring into Amperity via a courier has a corrupted archive. To resolve, you should upload a new file.
PGP encryption could not be decrypted	Data sources	This resolution option appears for decryption errors related to the provided PGP key in the file a courier is bringing into Amperity. Ensure that the PGP key is correct or that the file you are uploading to Amperity was correctly encrypted with the correct key and try again. This resolution may also indicate that an encrypted file was not fully copied when it was ingested. Re-copy the file and try again. If this continues to occur, consider revisiting the timing of when your files are dropped for ingestion by Amperity.
Google 2FA required	Campaigns, Orchestrations	This resolution option appears when the Google account you are using requires 2 Factor Authentication (2FA), but 2FA is not enabled in the account so Amperity is unable to continue. Follow the steps to access your Google account and enable 2FA, and then retry the campaign.
Google Ads user has insufficient permissions	Campaigns, Orchestrations	This resolution option appears when your Google Ads user does not have permissions to update audiences. Update this permission before retrying your workflow.
Google Ads account not set up	Campaigns, Orchestrations	This resolution option appears your Google Ads account might be in Draft mode or otherwise not set up. Complete your account setup and retry this workflow.
Google Analytics account deleted	Campaigns, Orchestrations	Select a new Google Analytics account to resolve this workflow.
Google Ads or DV360 missing PII	Campaigns, Orchestrations	This resolution option appears when you haven’t included PII in the data you send to Google Customer Match. Edit your query or segment to include the field(s) with PII and retry this workflow.
Insufficient permissions to update audiences	Campaigns, Orchestrations	This resolution option appears when the Google Ads user you are using doesn’t have sufficient permissions to update the audience. Follow the steps to access your Google account and ensure the user has sufficient permissions, and then retry the campaign.
Braze missing field	Campaigns, Orchestrations	This resolution option appears when you’re missing the external_id or braze_id field. Update your query or segment to include the field.
Facebook Security Challenge	Campaigns, Orchestrations	This resolution option appears if Facebook has issues a security challenge to this account. Follow the instructions given by Facebook to address the challenge.
Facebook Custom Audience Terms	Campaigns, Orchestrations	This resolution option appears when you have not yet agreed to Facebook’s custom audience terms. Accept the terms before resolving the error.
Missing Facebook External Identifier	Campaigns, Orchestrations	This resolution option appears when data you are trying to send to Facebook is missing the external identified column (EXTERN_ID). You can resolve this by going to the underlying query and adding in an EXTERN_ID column populated with unique identifiers. Amperity ID is commonly used. Retry the workflow/campaign after you have done this.
Facebook missing ad creation permissions	Campaigns, Orchestrations	This resolution option appears when your user does not have permissions to update the ad account. Update the permissions to include creating ads in the account.
Facebook ad account not part of a business	Campaigns, Orchestrations	This resolution option appears when you haven’t added this ad account to a business. Resolve this issue on Facebook before continuing your workflow.
Listrak name invalid	Campaigns, Orchestrations	This resolution option appears when Listrak couldn’t find the list name associated with this send. Update your destination to use a valid existing name and retry.
Listrak Authorization error	Campaigns, Orchestrations	This resolution option appears if Listrak denied authorization for the request from Amperity. Add the IP address for Amperity <https://docs.amperity.com/datagrid/destination_listrak.html#get-details> or update your Listrak credential before retrying your workflow.
SFMC missing primary key	Campaigns, Orchestrations	This resolution option appears when a required primary key for SFMC is missing. Update your query or segment and retry the workflow.
SFMC conflicting primary key	Campaigns, Orchestrations	You cannot edit the configured primary key of a data extension in Salesforce Marketing Cloud. Update or delete the configured data extension name that is sent to SFMC to apply your new primary key.
SFMC duplicate data extension names	Campaigns, Orchestrations	Salesforce Marketing Cloud requires data extension names to be globally unique across folders in SFMC. Update or delete the configured data extension name that is sent to SFMC to avoid naming collisions.
SFMC import file location not found	Campaigns, Orchestrations	Your import location must be a valid location within Salesforce Marketing Cloud. Verify that it exists and create it if it does not.
Zendesk authorization error	Campaigns, Orchestrations	Update your Zendesk credentials or confirm that the authorizer has the correct permissions to update users before retrying.