Workflow Modules
The Workflow Engine keeps long Agent runs alive through a restart or a pause, and generates recurring tasks from rules you set. Tasks arrive on time.
Runs
A long Agent run is checkpointed step by step. If the service restarts partway through, say during an overnight batch, the run picks up where it stopped and nothing already done gets replayed.
Run detail
The run holds its state at that step and waits. Once the shift lead answers, it continues from that exact step. The pause and the answer are both recorded.
Events
When one Agent finishes, another picks up the work automatically. Runs start from events raised inside the platform, not from someone remembering to kick one off.
Schedule
Set the rule once, for a daily gauge check or a weekly audit. The schedule generates each occurrence daily, weekly, monthly, or on an interval, marks anything overdue, and keeps a record of what got skipped.
Floor tasks
A generated task lands on the operator’s list for the shift. They do it on that screen, and the completion is recorded against the rule that created it.
Monitoring
There is no drag-and-drop screen for drawing a process. mode40 builds the run logic with you, and you own the recurrence rules, the schedule, and the record after that.
Not as a drawing on a screen: there is no visual workflow designer. mode40 builds the run logic with you, and the recurrence rules and the schedule are yours to set.
The run pauses at that step and holds its state. It continues from the same point once the person answers.
The run resumes from its last checkpoint. Nothing re-runs from the beginning.
It is marked overdue once its window passes. A task that is skipped is recorded as skipped, not removed.
30 minutes on your workflows and how the Workflow Engine resumes and pauses them.
We use cookies to understand how the site is used and to connect form submissions to earlier visits. No analytics or marketing cookies are set until you choose. Privacy Policy