# Operations that survive the restart

> TechFabric is a Temporal partner. We put durable execution under the operations that must not half-complete: a payment that charges but does not fulfil, a repossession that starts and is never recorded, a pipeline that dies mid-run. A step that fails at three in the morning resumes rather than restarts.

Canonical: https://www.techfabric.com/expertise/durable-execution-with-temporal

---

A queue delivers a message. Temporal keeps the state of the business process.

## What we build

- Durable workflows with complete, replayable execution history
- Existing APIs left in place and called as activities
- Human approval gates that survive a deploy
- Compensation paths designed in, not bolted on after the first incident

## Questions

### What problem does Temporal actually solve?

Any process with more than a few steps that must not half-complete. Temporal makes the workflow itself durable, so the process survives the infrastructure under it. The service line is /services/apis.

### Do we have to rewrite our services?

No. The usual pattern is a workflow in front of the sequence that already exists. Your APIs become activities. That is how we migrate a job chain without a rewrite.

### How is this different from a queue and retries?

A queue gives you delivery. It does not give you the state of a business process. Temporal keeps a complete, replayable history, so you can answer what happened without reconstructing it from logs.

### Do you work with Temporal Cloud or self-hosted?

Both. We have certified durable paths against Temporal Cloud, including a workflow that survived a full application restart and completed from its original history. Fabric Tower at /accelerators/fabric-tower uses that path for missions that park at approval.