Failure Flow
In FileFlows, users have the flexibility to create multiple failure flows to handle different error scenarios. However, only one failure flow can be designated as the default for all flow executions within the system. Users can choose which failure flow to use as the default, or they can opt not to use any failure flow at all.
During any flow execution within the system, if a default failure flow is set, it will be invoked to handle errors that occur. If no default failure flow is specified, the system will not utilize any failure flow to handle errors during flow execution.
A failure flow within FileFlows provides users with access to a limited set of flow elements, primarily focused on notifying users of a failure event. These flow elements typically include actions such as sending notifications via email, Discord, or other communication channels. The primary objective of a failure flow is to promptly inform users about errors encountered during the execution of other flows, ensuring timely awareness and response to any issues.
In addition to notification capabilities, failure flows also offer flexibility for users to execute custom functions and perform web requests as part of the error-handling process. This enables users to implement tailored error-handling logic, such as logging error details, gathering additional context, or triggering automated remediation actions.
By combining notification features with the ability to execute custom functions and web requests, failure flows empower users to implement comprehensive error-handling strategies within their FileFlows environment. This flexibility allows for efficient error detection, notification, and response, contributing to the overall reliability and effectiveness of workflow execution.
Default
Users can designate a specific failure flow as the default for all flow executions by toggling a setting within the configuration of that failure flow. When a failure flow is marked as the default, it becomes the primary mechanism for handling errors across all flow executions within the system.
Variables
A failure flow will have these additional variables available to it
| Name | Description |
|---|---|
| FailedElement | The name of the element that failed |
| FlowName | The name of the flow being executed |
| FailureReason | The reason for failure, if known |