Skip to content
Vareon

Back to a safe point after a failure.

After a failure, the job resumes from its last safe point.

Long-running tasks. It runs On an authorised request.

Frankfurt fails overnight, and the release picks up after London.

The release reaches Dublin and London, and the job marks a safe point after each.

Step 1 of 5: Two regions

A failure costs only the work since the last safe point.

After a failure, the job goes back to its last safe point and carries on from there. Everything finished before that point stays finished.

Step 1 of 3: The failure

The Frankfurt rollout fails at 02:10.

From failure to finished before morning.

The engineer fixes the cause, the job resumes from its safe point, and the release is done before the day starts.

Step 1 of 4: The failure

02:10: the Frankfurt rollout fails halfway, and the job stops at the failure.

Resuming after a failure is your team’s call.

A failed job waits where it stopped until someone authorised asks it to carry on. The request, and who made it, go on record.

Step 1 of 5: Authorised

The request comes from someone allowed to resume this job.

See it on your own work.

From your own assistant to every agent your company runs, a pilot puts Duplex on your own work, with the measures agreed before it begins.

vareon.com uses no analytics, advertising or third-party trackers, and Vareon does not sell your data. If you accept, the site remembers your light or dark appearance on this device for a year. If you deny, it stores only what it needs to work.

You can change your choice at any time under Privacy choices at the foot of every page. Read the privacy policy