# Workflows FAQ

[Stripe Workflows](https://dashboard.stripe.com/workflows) automates tasks and creates custom flows without code using a visual builder in the Stripe Dashboard. It's ideal for multi-step processes across Stripe products, increasing efficiency and enforcing business rules.
### Why can’t I access Workflows?
You must have the [administrator](https://docs.stripe.com/get-started/account/teams/roles#admin) or [developer](https://docs.stripe.com/get-started/account/teams/roles#developer) user role to read or create workflows.
### What are limits associated with Workflows?
* You can run up to 50 active workflows at a time.
* You can have a combined total of 50 active and inactive workflows.
* Each workflow can only have one trigger.
* Each workflow can support up to 50 steps, including actions and conditions.
* List conditions can evaluate up to 100 items.
  * Example: If conditions are set on a field containing a list of items, the workflow only checks the first 100 items to determine if the condition is met. Any items after that aren't evaluated.
### Why isn’t my workflow triggering?
**The workflow is inactive**: Even if an event matches your trigger, the workflow won’t run unless it’s active. Activate your workflow by finding it on [the Dashboard](https://dashboard.stripe.com/workflows), clicking the "**…**" icon and selecting **Activate**.
**The event doesn’t match your trigger conditions**: The incoming event might not satisfy the trigger’s defined conditions, such as amount thresholds or status.
**The event type isn’t being sent**: Check that the expected event is occurring by testing it manually or using Workbench to verify your event logs.
### Why don’t fields from previous steps show up?
* **The step didn’t run successfully**: If a previous step failed or was skipped due to a branch condition, it won’t produce any data to reference downstream.
* **You’re referencing the wrong step or field**: Make sure you’re selecting the correct step and using the correct field name.
* **The step output is empty**: If the upstream step returns no data due to a missing object or failed step, you’ll see missing or blank fields.
### If one step fails, does the whole workflow fail?
Yes, the whole workflow will complete with a status of failed.
### What happens to active runs if I update a workflow?
All active runs will complete using the workflow definition from when that run started. All newly triggered workflow runs will use the updated workflow definition.
### How can I pass data between steps in a workflow?
You can pass data between steps by dynamically referencing outputs from earlier steps. Select the "**+**" icon next to an action property’s input. A dropdown will display that allows you to reference previous steps’ data.
This allows you to chain logic together and build workflows that respond to real-time data.
### Why can’t I re-run my workflow?
You can only retry runs on active workflows, using their original event data for up to 30 days after the initial trigger was sent.
### When I re-run my workflow does it start from the step that failed?
No. Re-run workflows start from the very beginning, not from the previously failed step. All steps are re-run, even those that were completed successfully in the original run.
### Is the re-run idempotent?
No, re-runs are not idempotent. If your workflow includes actions like sending an internal email or updating a customer, those actions will be run again.
### Can I manually trigger my workflow?
Not yet. Currently workflows are fully event-driven and can only be triggered by public Stripe events. Future support is planned for manual triggers so you can start a workflow on demand.
### What happens if I accidentally move money?
Unfortunately, if the workflow ran correctly, no corrective actions are possible. Before activating a workflow, you must accept a warning message that indicates that moving money with workflows may occur.
### Will I get automatically notified when a workflow fails?
No, workflows don’t send automatic notifications when a run fails. You can view failed runs in [the Dashboard](https://dashboard.stripe.com/workflows/).
### Can I view past workflow runs? If so, for how long?
Yes, access to view past workflow runs in [the Dashboard](https://dashboard.stripe.com/workflows/) is guaranteed for up to 30 days. After that, runs may be cleaned up without notice.
### Does the 30 day limit for viewing workflow run data start from when the workflow was created or when it ran?
The 30 day window starts from the time the workflow run is completed. You’ll be able to view and inspect that run for 30 days from its completion time. After that, it may no longer be accessible, even if the workflow is still active.
### What happens to my workflow run history if I delete a workflow?
If you delete a workflow, all of its run history is permanently deleted.To retain your run history, deactivate a workflow rather than deleting it.
### Do workflows emit their own events such as workflow.succeeded or workflow.failed?
No. Workflows do not emit their own events. You can monitor your workflows using [the Dashboard](https://dashboard.stripe.com/workflows/), but there are no dedicated Stripe events triggered by a workflow’s success or failure.
### How long can a workflow run?
There is no fixed timeout for the entire workflow, but runs are generally short with most completing in a few seconds. The total duration depends on how long each step takes to run. Future support is planned for longer-running patterns such as long waits, delays, and scheduled actions.
### Can I call third-party APIs (external to Stripe) from my workflow?
No, workflows can only call APIs within Stripe. Future support is planned for calling third-party APIs, such as those provided by App Partners.
### Can I stop a running workflow?
No, once a workflow run starts, it continues running until it finishes. Workflows typically run very quickly, often completing in a few seconds..
### Why can’t I see the full workflow definition in a run, and instead only the execution path?
Future support is planned for versioning, which will allow you to view a snapshot of the entire workflow as it existed at the time of the run, including all possible paths.