Skip to content
Courses/Agents and automation/Persistent State and Crash Recovery

Persistent State and Crash Recovery

A 24/7 agent is not reliable because it never fails. It is reliable because it can crash, start again, and know what it was doing without improvising.

  • Separate conversation memory, task state, and durable knowledge.
  • Use checkpoints to resume workflows and audit decisions.
  • Know when to look at Temporal or durable execution for long-running processes.
Terminal
state_layers:
  hot:
    use: current step
    example: recent messages
  warm:
    use: task in progress
    example: active_tasks, checkpoint, summarized tool_outputs
  cold:
    use: durable memory
    example: preferences, validated facts, audit trail

boot:
  1: load active_tasks
  2: detect stale running tasks
  3: reconcile tool_executions
  4: request approval if uncertain
  5: resume or close with evidence
Complete Aulafy mapSee how this lesson fits without leaving your path.

Complete Aulafy map

How all courses connect

This is not a checklist. Start with the foundation, choose an outcome, and go deeper only when your project needs more control.

  1. 1Understand
  2. 2Apply or build
  3. 3Operate with confidence
01

Choose an application

Turn the foundation into a visible outcome: a website, a business improvement, media, or an interactive experience.

Continue into the technical branch when you need to maintain code, data, or infrastructure.

02

Build with code

Prepare your environment, work with coding agents, and run models while keeping control of your projects.

This branch prepares you to design and operate reliable AI systems.

03

Take systems to production

Combine retrieval, agents, evaluation, security, deployment, and model adaptation when the problem requires it.

You do not need every course: choose the component your system needs and return as it grows.

View full catalogue