Success Action
The Success Action node forces a workflow to finish successfully even if a previous node has failed.
It is typically connected to the fail output of another node. When triggered, the node converts the failure state into a successful one, allowing the stream to continue and complete without being marked as failed.
Behavior
Overrides a failure state
Marks the stream as successful
Does not retry or fix the failed operation
Produces no additional output or data
This node does not solve the error — it only prevents the workflow from stopping because of it.
Typical Use Cases
non-critical file operations (e.g., optional copy or cleanup)
external system unavailability that should not block a workflow
user or project creation workflows
background automation where the main action must always complete
Example Scenario
A stream triggered by CREATE_USER copies a template configuration file to the user directory.
The user account is only created if the stream finishes successfully. If the copy operation fails (e.g., storage temporarily unavailable), the entire stream would fail and the user would not be created.
By connecting the fail output of the copy node to a Success Action, the stream still completes successfully and the user is created — even if the copy did not happen.
Important Warning
Using this node hides real errors.
If a failed operation is critical (for example media delivery, archiving, or database updates), the problem may go unnoticed and lead to missing files, incomplete workflows, or inconsistent systems.
Practical Tip
Use this node only for non-essential steps. If you find yourself placing it after important operations, that’s usually a sign the workflow should instead include proper error handling, retry logic, or conditional checks rather than suppressing the failure.
Last updated