Learn
Can an AI agent run a process that takes weeks?
What breaks when a process waits on a person for days, and what a platform needs to survive it.
The short answer
Yes, but only if the platform treats waiting as a normal state rather than an error. Most automation assumes a process starts and finishes in one session. Real enterprise work does not.
Why enterprise work waits
A process waits on a vendor who has not returned a quote, on an approver who is on leave, on a quarter close, on a legal review that has to queue behind other reviews. The waiting is not an exception to the process; it is most of the elapsed time in it.
The failure modes
- Sessions time out while the process is legitimately idle.
- Context is lost, so whoever picks the work up has to reconstruct what happened.
- State is rebuilt by hand, which introduces differences between the run and the record.
- The run restarts from the beginning, repeating work that already completed.
Where VeroTX sits
WorkStreams hold state across days or weeks and resume with full context, so a step that waits on a person picks up exactly where it left off. Failed runs resume from the point of failure rather than from the start. A run finishes on the Playbook version it began on, so a change made mid-flight does not rewrite the rules an in-progress run is executing under.
Where to next
Read deeper
Product and platform pages on the same topic, drawn from the VeroTX knowledge base.
Search everything in one place in the Research Center, or ask Veroli, which answers from the same knowledge base.