Skip to main content
Part of Invoice exceptions from complete data releases.

​
Complete stack

​
Connections

  • bijection → postgres: Transactional release selection and decisions. Identity: Backend database credential.

​
Deployment inputs

  • backend (file, required): Native Bijection backend executable.
  • cli (file, required): Bijection CLI executable.
  • sdk (directory, required): Built Bijection SDK directory.

​
Bounds and cleanup

One local backend and owned PostgreSQL cluster; at most 256 invoice lines, eight releases and 32 reviews. Maximum duration: 1200 seconds. Maximum captured log: 4194304 bytes. Estimated cost: No provider runtime charge. Cleanup: Stop the exact backend and owned PostgreSQL cluster, remove run credentials, and verify the receipts. The executable runbook is maintained at examples/sales-exceptions/recipes/bounded-etl/runbook.md. A declared journey is verified only when every named check appears in a successful execution report and cleanup has been observed.