Diagnose Failed Plan Runs
This section provides information and references on how to identify and repair issues that have led to failures in a plan run.
Identify Plan Run Failures
Definition
A plan execution has failed if any individual task in the plan run fails. If so, the plan run is marked as failed in the application.
After a task has failed, plan execution could still continue if the plan logic includes On failure tasks from the task that did fail.
Anmerkung
Plans are permitted to run for up to 48 hours, after which they are marked as failed.
Failure messages
When a plan run fails to complete, a failure message appears in following locations:
Plans Page: Listing for the plan.
Plan Runs Page: Listing of individual plan runs.
The following is an example from the Plan Runs page:
 |
Anmerkung
Displays all the jobs for the last 180 days.
Figure: Plan run failed
Retry Failed Plan Runs
When a plan run fails, you can rerun the plan You can retry failed plan runs by clicking the Retry from failed button. For more information, see Plan Run Details Page.
By Task Type
Anmerkung
A plan run is essentially a sequence of tasks that are executed based on the outcome(s) of previous tasks. Failures are likely to be the result of failures to execute individual tasks. Please use the links below to explore information for specific tasks.
The following types of tasks can be executed as part of a plan in the Alteryx Analytics Cloud:
Flow task: An ad-hoc or scheduled execution of the transformations required to produce one or more selected outputs from a flow.
Snapshot: An image of the flows, recipes, and datasets of the flow tasks in a plan, taken at the time of plan execution.
Trigger: A trigger is a scheduling object that launches a plan run at a user-defined time.
HTTP task: A request submitted to a third-party server as part of a plan run.
Slack task: A specialized version of HTTP task, a Slack task can be configured to delete a message to a specified Slack channel.
Delete task: You can specify a task to delete one or more files on backend storage. This task type is useful for removing intermediate files that are generated as part of job or plan execution.
For more information, see Plan View Page.
For more information on plans in general, see Overview of Orchestration.
Contact Support
If you are unable to diagnose your plan run failure, please contact Alteryx Support.
Report an Issue
If you believe that your job has failed due to an issue with the Alteryx Analytics Cloud, select Resources menu > Report issue to alert Alteryx Support.