Retry on fail except for known error Template

This workflow is ideal for:

• Developers looking to implement retry logic in their applications.
• Data engineers who need to ensure data retrieval processes are robust against transient errors.
• Business analysts wanting to automate workflows that deal with known error scenarios without manual intervention.
• Operations teams managing critical data pipelines that require reliability and error handling.

This workflow addresses the following issues:

• Transient errors: Automatically retries operations that fail due to temporary issues, thus increasing success rates.
• Known errors handling: It differentiates between known errors and other failures, allowing for appropriate responses without unnecessary retries.
• Retry limits: Prevents infinite loops by implementing a limit on the number of retries, ensuring system stability and resource management.

The workflow operates through the following steps:

1. Manual Trigger: Starts the workflow manually, allowing users to initiate the process when needed.
2. Set Tries: Initializes a counter for the number of attempts made to execute the operation.
3. Replace Me: This node represents the main operation that needs to be performed. If it fails, the workflow will handle it based on the error type.
4. Catch Known Error: Checks if the error returned is a known issue (e.g., 'could not be found'). If so, it routes to the Known Error node.
5. Wait: Introduces a delay before retrying the operation, allowing for transient issues to resolve.
6. Update Tries: Increments the attempt counter after each failure.
7. If Tries Left: Evaluates if the number of attempts is less than the defined maximum (default is 3). If attempts are left, it retries; if not, it proceeds to stop the workflow with an error message.
8. Retry Limit Reached: Stops the workflow and outputs an error message if the maximum retry limit is reached.
9. Success: If the operation succeeds, it proceeds to this node, indicating a successful workflow execution.