---
id: TST-PFM-INT-007
title: raise
kind: integration
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/tests/integration/raise.integration.spec.ts
implements:
  - ATS-PFM-INT-020-06
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: >-
  Use the suite-owned database fixtures and its declared cleanup; prepare the test database before
  integration or lifecycle execution.
evidence:
  - 'macroservice-libraries:packages/workflow-actions/src/tests/integration/raise.integration.spec.ts'
test_cases:
  - source: >-
      macroservice-libraries:packages/workflow-actions/src/tests/integration/raise.integration.spec.ts#writes
      a run per matched spec: the inline one executed, the durable one queued, the false condition not
      matched
    provenance: test
  - source: >-
      macroservice-libraries:packages/workflow-actions/src/tests/integration/raise.integration.spec.ts#with
      the host’s facts declared, a condition over a declared fact is evaluated as before
    provenance: test
  - source: >-
      macroservice-libraries:packages/workflow-actions/src/tests/integration/raise.integration.spec.ts#refuses,
      without a throw, a spec whose condition reads a fact the host did not declare for the point: no
      run, a problem
    provenance: test
  - source: >-
      macroservice-libraries:packages/workflow-actions/src/tests/integration/raise.integration.spec.ts#gives
      each run the deterministic id of its instance, occurrence, key and occurrence number
    provenance: test
  - source: >-
      macroservice-libraries:packages/workflow-actions/src/tests/integration/raise.integration.spec.ts#queues
      the durable runs under one batch row, the batch’s ordered lane
    provenance: test
  - source: >-
      macroservice-libraries:packages/workflow-actions/src/tests/integration/raise.integration.spec.ts#schedules
      the instance’s timers when it opens: P2D business from a Friday 16:00, and unscheduled for an empty
      field
    provenance: test
  - source: >-
      macroservice-libraries:packages/workflow-actions/src/tests/integration/raise.integration.spec.ts#an
      exit cancels the instance’s unscheduled timer too, which never had an instant (fixed in 0.2.0: the
      check refused it)
    provenance: test
  - source: >-
      macroservice-libraries:packages/workflow-actions/src/tests/integration/raise.integration.spec.ts#a
      guard refusing a host action outside the sweep records the run failed with the problem and
      attention; the command stands
    provenance: test
  - source: >-
      macroservice-libraries:packages/workflow-actions/src/tests/integration/raise.integration.spec.ts#writes
      nothing on a repeated raise of the same occurrence: it finds its rows
    provenance: test
  - source: >-
      macroservice-libraries:packages/workflow-actions/src/tests/integration/raise.integration.spec.ts#refuses
      the pool: the library writes only inside the host’s transaction
    provenance: test
  - source: >-
      macroservice-libraries:packages/workflow-actions/src/tests/integration/raise.integration.spec.ts#an
      indeterminate condition raises attention under retry_then_attention, and is skipped under
      retry_then_skip
    provenance: test
  - source: >-
      macroservice-libraries:packages/workflow-actions/src/tests/integration/raise.integration.spec.ts#writes
      nothing when the host’s command fails after raising: the transaction rolls back (07 §6.3 point 5)
    provenance: test
  - source: >-
      macroservice-libraries:packages/workflow-actions/src/tests/integration/raise.integration.spec.ts#an
      inline action’s failure fails the host’s command, and nothing is written
    provenance: test
  - source: >-
      macroservice-libraries:packages/workflow-actions/src/tests/integration/raise.integration.spec.ts#refuses
      a spec validated against a contract version its type no longer accepts
    provenance: test
  - source: >-
      macroservice-libraries:packages/workflow-actions/src/tests/integration/raise.integration.spec.ts#another
      tenant’s runs and timers are invisible under row-level security
    provenance: test
dependency_evidence:
  provenance: test
  source: 'macroservice-libraries:packages/workflow-actions/src/tests/integration/raise.integration.spec.ts'
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# raise

## Verification Boundary

This database and service suite exercises raise. 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

In-process execution does not establish deployed infrastructure or a real provider response. Several bindings can supply different parts of a detailed scenario; no single-file completeness is implied.

## Real Dependencies and Test Doubles

The suite definition identifies its database fixtures and replaced clients, hooks, clocks or executors. Integration runs use the prepared database; lifecycle runs exercise the in-process route or adapter path.

## Must Not Be Doubled

The database constraints, transactions and service behavior claimed by an integration binding must execute. Replaced external seams cannot establish live provider or infrastructure behavior.