---
title: "Temporal | Skills We Assign For | Azendo"
description: "Temporal for durable execution — workflows as code, determinism, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/temporal/"
---

[Skills](https://azendo.co/skills/) Automation platforms 

# Temporal.

Temporal is a durable execution platform. Workflow code is written in an ordinary language and the platform guarantees it runs to completion despite failures, persisting execution state and replaying it on recovery.

## Where Temporal fits on a long engagement.

Writing workflows as ordinary code is the property that makes Temporal different. Loops, conditionals and error handling are language constructs rather than diagram elements, and the platform makes that code durable — a process can sleep for thirty days and resume correctly, surviving deployments and crashes.

The constraint is determinism. Workflow code is replayed from history on recovery, so it must produce the same result each time — no direct clock reads, no random values, no external calls outside activities. Violating that produces failures that are confusing until the model is understood.

## What an assigned team does with Temporal.

Versioning long-running workflows is the operational subtlety. A workflow running for weeks may need its code changed while instances are in flight, and the platform provides versioning primitives that have to be used deliberately.

Planning for that before the first long-running workflow ships is the kind of foresight a standing assignment provides, as described in [how an assignment runs](https://azendo.co/how-it-works/).

## What we use Temporal for.

* Processes spanning days or weeks Durable execution that survives deployments and restarts.
* Retries and timeouts without plumbing Failure handling provided by the platform rather than implemented per process.
* Versioning planned for in-flight instances Code changes handled deliberately while long-running workflows are live.

## How Temporal capacity is assigned.

Durable execution work is assigned under [software development outsourcing](https://azendo.co/services/software-development/), with workflow versioning planned before long-running processes go live.

## Service lines it sits in

* [AI automation engineering](https://azendo.co/services/ai-automation-engineering/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in automation platforms

* [Zapier — skill we assign for](https://azendo.co/skills/zapier/)
* [Power Automate — skill we assign for](https://azendo.co/skills/power-automate/)
* [UiPath — skill we assign for](https://azendo.co/skills/uipath/)
* [Automation Anywhere — skill we assign for](https://azendo.co/skills/automation-anywhere/)
* [Blue Prism — skill we assign for](https://azendo.co/skills/blue-prism/)
* [Workato — skill we assign for](https://azendo.co/skills/workato/)
* [MuleSoft — skill we assign for](https://azendo.co/skills/mulesoft/)
* [Boomi — skill we assign for](https://azendo.co/skills/boomi/)

## Tell us what your roadmap needs Temporal for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)