Publishing a workflow doesn't start it — you decide when it runs and set a ceiling on how much it does.
Live and Inactive
The Live / Inactive toggle in the top bar controls whether a published workflow runs. When it's Live, the workflow fires on its trigger. When it's Inactive, it's paused — nothing new enrolls, though runs already in progress finish.
Run manually anytime
Whatever the toggle, you can run a workflow on demand with Trigger workflow — useful for testing before you go Live.
Set a run limit
In the workflow's Settings, turn on Set a total run limit and enter a maximum number of runs. Manual, scheduled, and trigger runs all count toward it. When the limit is reached, the workflow pauses automatically.
Let the Assistant start it from chat
In Settings, turn on Let the assistant start this workflow to let Ocean's chat Assistant run this workflow when someone asks for it by name — a company or person the chat is already discussing can seed the run directly. It's on by default once a workflow is published, and needs a published version before you can turn it on. Runs started this way show as Assistant in Runs. Credits and plan limits apply the same as any other run.
Turn it off for a workflow you only want to start yourself — from a schedule, an event, or your own click.
Why a workflow paused itself
A workflow pauses itself for one of two reasons, shown as a distinct subtitle in the workflow list so you don't have to open it to find out which:
Run limit reached — it hit the ceiling you set. Raise the limit or clear it to let it run again.
Ran out of credits — your workspace ran out of credits mid-run. Ocean emails your workspace admins when this happens. Records already in flight when this happens show as Blocked in Activity, not Failed — they pick up automatically once you top up credits and resume the workflow.
Best practice
Set a run limit on a new workflow while you watch its first runs, then lift it once you trust it.
Keep a workflow Inactive until you've reviewed a test run in Activity.