Durable Runtime
One task.
Weeks or months of work.
Built-in Temporal retains workflow state through waits and interruptions. Corin can continue the same work item when a reply arrives or a configured step is retried.
Durable Runtime / Example work itemRevised quote request
The request becomes one work item.
Agents begin with permitted records and the relevant procedure. The workflow records the completed step and what comes next.
What durability means here
The task keeps its place.
An agent can finish one step and wait for a person or an external system. Corin keeps the same work item open across that wait. When the expected input arrives, work can resume at the pending step.
Built-in Temporal supports the workflow state, waits and resumption in supported flows. The model is called for the steps that need it; it does not run throughout a weeks-long wait.
Waits are part of the workflow
A reply can arrive weeks later.
In the quote example, the team asks for a missing customer detail. The task records what it already checked and waits. A later reply belongs to Q-1042, so the agents can continue with the updated information.
The same pattern applies when a person must approve a decision. The approval is a new input to the open task, within its permissions.
The pricing analyst checks the permitted records and asks for a missing detail.
A configured retry can repeat the failed step.
A temporary tool timeout need not erase the completed work. The workflow records the attempt and follows its configured retry policy.
Retries and failures
Retry a failed step when safe.
Temporal supports retries and recovery from infrastructure interruptions. A Corin workflow still needs to define which failed operations may be retried, when to stop, and when to ask a person to resolve a business exception.
If an external write may have succeeded before a timeout, repeating it could create a second action. A manager's rejected quote also needs a revised decision, not another automatic attempt.
Inspect what happened
Three records answer different questions.
Durable execution, agent telemetry and the business system each show a different part of the work.
Temporal state
Which step completed, what is pending, and what event or retry advances the work?
Langfuse telemetry
Which agent, model and tools were used, and what did the run cost or take in time?
Business record
Who approved a decision, and what actually changed in the connected system?
Build with Corin
Try a task with a real wait.
Use the developer starting point to inspect a supported workflow. Adapt its waits, retry boundaries and approvals to a task of your own.