Create Accountor Login
Docs

Run Progress

Part of the MountDev Ops Workflows documentation. Updated November 21, 2026

MountDev Ops Workflows documentation | Updated November 21, 2026

Our Commitment MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.

A long workflow can say how far along it is. Name the steps the work goes through, add an Update Progress step wherever the work moves on, and the latest progress of each run is kept with the run.

Progress Steps

Each workflow can list up to 12 Progress Steps, with up to 60 characters each, in plain words. For example, a month end close might list Pulling the bank feeds, Matching payments, Building the reports, Checking the totals, and Filing the summary.

  • Progress Steps are saved with the workflow. Changing them follows the same rule as any change to a workflow: a run that is already going finishes as it began.
  • A label that looks like a key or a password is refused when the workflow is saved.

Update Progress

Update Progress is a step like any other, and it is free: it counts nothing in Background work. It has these fields:

  • Step: one of the workflow's Progress Steps.
  • State: Waiting, Working, Done, or Did Not Finish.
  • Percent: Automatic (steps done out of steps named), or a number from 0 to 100.
  • Note: up to 80 characters, in your own words. A note is never what another step returned, and a note that looks like a key is refused when the workflow is saved and again when it runs.
  • Tie to a Client: optional. A CRM company the progress belongs to. A run that already has a company, such as a client's request, starts tied to it.

A workflow saved by your own AI assistant is always off, like every workflow, and only a person turns it on.

How Progress Moves

  • One way forward. The percent never goes down. A Done step never goes back. A step that did not finish can be set to Working again only when the workflow tries it again, for example after Run Again.
  • Older reports change nothing. Each report carries a number, and a report with an older number than the latest is ignored.
  • Calm writes. At most one write a second for each run. Reports inside the same second are combined and the last one wins. The first Done or Did Not Finish for a step is always written at once. A run keeps at most 200 progress reports.
  • A test run writes nothing. Test Run and Test With Sample Data show what the step would do and keep no progress.
  • A run that ends keeps its last progress. A run that ends with a step still Working shows that step as Did Not Finish. The run itself is unchanged.

Report Back to the Client

In a client action's run, the step Report Back to the Client carries progress to the client who asked, the same way Update Progress carries it to your own Home. It gains three fields:

  • Steps to Change. Zero or more pairs of one of the action's named steps and a state: Waiting, Working, Done, or Did Not Finish. A name that is not one of the action's steps is refused when you save the workflow and again when it runs.
  • Step Note. An optional note of up to 80 characters for a step, shown under it, such as "About 2 minutes". A note that looks like a key is refused and the step fails with a plain sentence.
  • Percent. Automatic (steps done out of steps named, in whole numbers) or a whole number from 0 to 100. The bar only moves forward.

A client's steps follow the same one way rules as above. Reports are sent at most once every 5 seconds for a request, with the first Done or Did Not Finish sent at once, and a request sends at most 60 progress messages. When a step is Did Not Finish and the request is still Running, the client gets one notice. The client never sees the provider's error text. The full rules are in Client Actions.

Watch It on Home

The Run Progress widget on Home follows a workflow's newest run, or one run, with a bar and each step, live. Add it from Add Widget under Workflows, or press Watch on Home on a run in Run History. See Run Progress on Home.

A Client's Request

When a client starts one of your client actions, the Report Back to the Client step also fills that run's progress row, tied to the client's company, so you can watch the client's request on your own Home with the Run Progress widget. There is one record of progress for the run, never two: it follows the steps and percent the action names, one way forward. See Client Actions.

Show It to a Client

Add a Run Progress widget to a client dashboard as client data, and each client sees the newest run of that workflow tied to their own company: the percent, your step names, their states, and your notes, never a run number, a result, or an error. Only an owner or admin publishes it, and View As shows exactly what a client sees. See Dashboards.

What Is Kept

One row for each run, in your own account: the run's state, the percent, each step's name, state, and note, the time it started, and the time it last changed. Nothing about what a step returned, no error text, and no key. The row is kept as long as its run is kept, and it is part of Export Everything as Workflow Run Progress.

For Your AI Assistant

The action workflows.progress.read, with the tool workflows_run_progress, reads the latest progress of a workflow's newest run (give the workflow), or of one run (give the run). It needs the same permission as Run History. workflows_save takes progress_steps and the Update Progress step, and always saves off. No tool adds a widget or shows progress to a client.

Ask Us Anything

We’d love to hear from you!