Recurring process automation
A recurring process runs the steps that were defined, and it starts only when the scheduled time or the business event says to. A failure or an exception goes to a person. The trigger is a time or an event you name, not a standing loop.
What goes in
The defined steps, the schedule or event that starts them, the systems those steps use, and the person who should receive exceptions. Progress is written down at each defined step.
What the engine does
- Start when the agreed time or event occurs.
- Run the defined steps in order.
- Record progress and any failure.
- Route exceptions to the right person.
What your team receives
A record of what ran, what failed, and what was sent to a person. Steps that were not defined do not run. The log shows the step that stopped, and the exception goes to the person assigned to it.