---
id: TST-PFM-INT-639
title: Workflow timer transitions
kind: unit
product_area: platform
module: integrations
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: macroservice-libraries
files:
  - packages/workflow-actions/src/timer-states.spec.ts
implements: []
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: 'The test process owns its inputs, fake clocks and any replaced runtime ports.'
test_cases:
  - provenance: test
    source: >-
      macroservice-libraries:packages/workflow-actions/src/timer-states.spec.ts#has exactly the eight
      statuses and the ten events of 08 §4, and a cell for each pair
  - provenance: test
    source: >-
      macroservice-libraries:packages/workflow-actions/src/timer-states.spec.ts#unscheduled: the fact
      being set schedules it; a host’s supersede supersedes it; an exit cancels it; nothing else applies
  - provenance: test
    source: >-
      macroservice-libraries:packages/workflow-actions/src/timer-states.spec.ts#scheduled: a pause pauses
      it, the sweep claims it, a host’s supersede supersedes it, an exit cancels it; nothing else applies
  - provenance: test
    source: >-
      macroservice-libraries:packages/workflow-actions/src/timer-states.spec.ts#paused: a resume
      schedules it again, a host’s supersede supersedes it, an exit cancels it; the sweep never claims it
  - provenance: test
    source: >-
      macroservice-libraries:packages/workflow-actions/src/timer-states.spec.ts#claimed: a lapsed claim
      schedules it again; the firing fires, supersedes or blocks it; an exit does not cancel it
  - provenance: test
    source: >-
      macroservice-libraries:packages/workflow-actions/src/timer-states.spec.ts#blocked: staff retry
      schedules it again, a host’s supersede supersedes it, an exit cancels it; nothing else applies
  - provenance: test
    source: >-
      macroservice-libraries:packages/workflow-actions/src/timer-states.spec.ts#fired: terminal, no event
      applies
  - provenance: test
    source: >-
      macroservice-libraries:packages/workflow-actions/src/timer-states.spec.ts#cancelled: terminal, no
      event applies
  - provenance: test
    source: >-
      macroservice-libraries:packages/workflow-actions/src/timer-states.spec.ts#superseded: terminal, no
      event applies
  - provenance: test
    source: >-
      macroservice-libraries:packages/workflow-actions/src/timer-states.spec.ts#statusesAccepting gives
      each event the statuses it applies to, which the SQL guards use
  - provenance: test
    source: >-
      macroservice-libraries:packages/workflow-actions/src/timer-states.spec.ts#every event has one
      target status
  - provenance: test
    source: >-
      macroservice-libraries:packages/workflow-actions/src/timer-states.spec.ts#canTransitionTimer agrees
      with the table, and the terminal statuses are fired, cancelled and superseded
evidence:
  - 'macroservice-libraries:packages/workflow-actions/src/timer-states.spec.ts'
---
# Workflow timer transitions

## Verification Boundary

This unit suite exercises workflow timer transitions within the shared package. It records engineering coverage at the pinned revision without claiming a deployed run.

## What This Suite Proves

The source assertions cover the package behavior under controlled inputs. No detailed capability or feature scenario binding is verified in this registration.

## What It Does Not Prove

The suite does not establish deployed authorization, database behavior, provider effects or a complete customer workflow.

## Real Dependencies and Test Doubles

Imported package functions execute against the source-defined fixtures. Runtime ports, clocks and external transport responses remain controlled wherever the suite replaces them.

## Must Not Be Doubled

The shared function under test and its result assertions must execute. Returning an expected answer from a substitute does not prove the package behavior.