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, which includes users who are assigned the DataGrid Operators policy. The Workflows page is not available to users who are only assigned the AmpIQ Users 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 60 seconds and updates the status of any workflow that is currently in-progress.

The workflow tab, showing a completed workflow.

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.

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.

The workflow tab, showing a workflow with errors.

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 optios, open the failed workflow, and then click Show Resolutions. A page opens that describes the error, and then provides a list of options.

The workflow tab, showing a workflow with errors.

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 Customer Match 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. Verifyt that it exists and create it if it does not.

Zendesk authorization error

Campaigns, Orchestrations

Update your Zendesk pcredentials or confirm that the authorizor has the correct permissions to update users before retrying.