---
id: TST-PFM-INT-578
title: execution timeouts
kind: unit
product_area: platform
module: integrations
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-platform
files:
  - modules/integrations/tests/unit/services/execution-timeouts.spec.ts
implements:
  - ATS-PFM-INT-010-04
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: Pure test fixtures owned by the test process.
evidence:
  - 'services-platform:modules/integrations/tests/unit/services/execution-timeouts.spec.ts'
test_cases:
  - source: >-
      services-platform:modules/integrations/tests/unit/services/execution-timeouts.spec.ts#is 24 hours
      for an async-only capability whose manifest declares none
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/execution-timeouts.spec.ts#is 24 hours
      when the manifest declares a zero or negative budget
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/execution-timeouts.spec.ts#is the
      manifest’s explicit async_timeout_ms (the Dummy declares 60 s)
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/execution-timeouts.spec.ts#is never
      raised above 24 hours by the manifest
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/execution-timeouts.spec.ts#is not
      overdue a moment before its budget is spent
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/execution-timeouts.spec.ts#is overdue at
      started_at plus its budget, async_timeout
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/execution-timeouts.spec.ts#is measured
      from the attempt the adapter accepted when earlier attempts failed
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/execution-timeouts.spec.ts#is overdue at
      started_at plus its budget, async_timeout
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/execution-timeouts.spec.ts#is not
      overdue within the sync budget and its grace minute
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/execution-timeouts.spec.ts#is overdue
      past the sync budget plus a grace minute, attempt_lost
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/execution-timeouts.spec.ts#bounds an
      async attempt by the consumer’s longest attempt plus a grace minute
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/execution-timeouts.spec.ts#is overdue
      past the sync budget plus a grace minute, attempt_lost
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/execution-timeouts.spec.ts#is not
      overdue within the longest queued wait after its last change
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/execution-timeouts.spec.ts#is overdue
      past the longest queued wait after its last change, dispatch_lost
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/execution-timeouts.spec.ts#is never
      overdue while a dispatch row waits for the dispatcher
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/execution-timeouts.spec.ts#is never
      overdue: only an execution in flight is timed out
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/execution-timeouts.spec.ts#is class
      unknown with the kind’s code, async_timeout being unknown.async_timeout
    provenance: test
dependency_evidence:
  provenance: test
  source: 'services-platform:modules/integrations/tests/unit/services/execution-timeouts.spec.ts'
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# execution timeouts

## Verification Boundary

This unit suite exercises execution timeouts. Its registration records the executable definition; no run result is asserted.

## What This Suite Proves

The bindings identify the detailed outcomes asserted by this suite. Test-level evidence retains the individual checks, including cases where several suites contribute to one scenario.

## What It Does Not Prove

Pure cases do not establish database constraints, deployed authorization or provider effects.

## Real Dependencies and Test Doubles

The suite evaluates its imported functions with controlled inputs. Its source records the fixture and substitution boundary.

## Must Not Be Doubled

The function under test and its result checks must execute. Replacing them with expected answers provides no proof.