The Flows app gives you a single place to see exactly where every project stands in its automation — which actions have run, what's coming next, and anything that needs your attention. This article covers reading that progress at a glance and stepping in to manage individual actions when you need to.
Where to find your flows
You can reach the Flows app from anywhere in Dubsado, and also from inside any individual project.
From the main sidebar: Click Flows in the main navigation to open the Flows app and see all flows across every project in your workspace.
From a project: Open a project and click the Flows tab to see only the flows associated with that project.
Both paths take you to the same flow list — the difference is scope. The global view shows every flow across all projects; the project view is pre-filtered to that project.
Reading the flow list
The flow list is your at-a-glance view of every active and completed automation. Each entry in the list shows the project name (with its project icon), the flow title, a preview of the next action scheduled to fire, and a progress bar indicating overall completion.
When all actions in a flow are done, the next-action preview shows All actions complete with a green checkmark. If a flow is paused, you'll see a pause icon in that spot instead.
Filtering and sorting
The left navigation in the Flows app surfaces pre-filtered views so you can zero in on what matters most. Each view focuses on a specific state:
All Flows — every flow applied across all projects, regardless of status
Approval Required — flows that contain at least one action waiting on your manual approval
In Progress — flows currently running and waiting for an action to complete
Paused — flows where automation has been temporarily stopped
Errored — flows where an action has failed and needs attention
Complete — flows where every action has run successfully
Approval Required and Errored are the two views worth checking regularly. They surface the flows that need you directly — approvals waiting on your go-ahead and actions that have failed and need a fix.
Flow templates are managed in a separate area of the Flows app. For details on creating and editing flow templates, see that article.
You can sort the list by Title or Recent in ascending or descending order. In the global view, use the Project filter to narrow the list to flows from a specific project. Inside a project's Flows tab, the list is already scoped to that project, and a search box replaces the project filter.
Understanding the progress bar
Each flow entry displays a progress bar made up of colored segments. Each segment represents one action in the flow, in order from left to right. The color of a segment tells you where that action stands:
Green — the action has completed successfully
Blue — the action has triggered and is waiting due to a delay or scheduled send date (for example, "2 days after project start")
Gray — the action has not yet triggered
Purple — the action is waiting for your manual approval before it can proceed
Red — the action has failed
Faded orange — the action was skipped (marked complete without running)
Viewing a flow's actions
Clicking any flow in the list opens a detailed node-based visualization of the flow. Each action appears as a card connected top to bottom in order. The flow header shows a status badge — In Progress (blue), Paused (orange), or Complete (green) — so you know the flow's overall state at a glance.
Each action card displays its status directly, so you don't need to hover to see when an action ran:
Completed on [date] (green) — the action ran and the date it completed
Sending on [date] (blue) — the action is queued and will fire at the shown date
[Action name] — Waiting for approval (purple) — the action is holding for your approval
A red error message (for example, "Action failed - retry needed") — the action failed
Skipped on [date] (orange) — the action was manually skipped
A trigger description such as "Immediately when all previous actions complete" or "2 days after project start" (gray) — the action hasn't triggered yet and is showing its waiting condition
The flow header also contains controls for managing the flow itself — Pause / Resume, Edit, and Delete. For details on how to pause, resume, or delete a flow, see the article on managing your flows. This article focuses on reading and managing individual action nodes.
Managing individual actions
Each action node in the flow visualization may show one or more icon buttons depending on the action's current state. These controls let you step in and take manual action when automation alone isn't enough.
Force now
Force now immediately runs a pending action, ignoring any delay or timing rule configured for it. It appears on actions that have not yet run and have not failed.
Use Force now when you don't want to wait for the action's scheduled trigger — for example, when a client meeting went ahead of schedule and you want the follow-up email to go out right away.
Skip and mark complete
Skip and mark complete marks an action as finished without actually running it. It's available on any action that hasn't run yet.
Skipping an action marks it complete without sending or running it. If the action was configured to send something to the client, the client will not receive whatever that action would have sent. If the action was configured to assist with project management, that internal action will also not execute automatically.
Use Skip and mark complete when you've already taken care of something manually — for example, you sent a check-in email directly from your inbox and don't need Dubsado to send it again.
Approve
Approve appears as a purple button on actions configured to require manual approval before firing. Clicking it allows the action to proceed. These actions are also surfaced in the Approval Required view so they're easy to find.
Retry
Retry appears on failed actions in place of Force now. If an action shows a red error state, fix the underlying issue first (for example, a missing email template or an incorrect trigger configuration), then click Retry to attempt the action again. For guidance on diagnosing specific errors, you can troubleshoot the error by checking out the flows errors article.
Once an action has run or been skipped, no manual controls appear on it. Completed and skipped actions cannot be re-triggered or undone from this view.
FAQ
Why isn't an action firing when I expected it to?
There are a few common reasons an action might not have fired yet. The action may still be waiting on its trigger condition — a blue "Sending on…" banner means it's queued and will fire at the shown date, while a gray trigger description means its condition hasn't been met. The flow may be paused — check the Paused view and resume it if needed. The action may also be waiting on your approval — check Approval Required and click Approve. Finally, if the action is timed to fire outside your configured active hours, it will hold until the next active period begins.
One of my actions shows red. What do I do?
Open the Errored view, then click into the flow. Find the action showing a red error banner and read the error message — it describes what went wrong. Fix the underlying issue (such as a missing template or a broken trigger), then click Retry on that action. For more detailed troubleshooting steps, see the article on how to troubleshoot the error.
What does a faded orange segment mean?
A faded orange segment in the progress bar means that action was skipped — you or a team member used Skip and mark complete on it. The action was marked finished without actually running, so the client did not receive whatever it would have sent.
Can I edit an action that already ran?
No. Once an action has run or been skipped, it's locked and shows no manual controls. If you need to make a change, you can add a new action in the flow editor. For how to edit, add, or remove actions on a running flow, see managing your flows.
