Conversation
added 9 commits
September 25, 2026 13:09
Add a Payload Mapping section to Pollable Outbound: enqueue-time evaluation, bindings, object output, mapping_version, failure handling per poison_policy, redrive with reapply_mapping, the mapping preview endpoint and a multi-organization example. Document the org_id and mapping_version envelope fields, late-arrival re-keying with MSG_LATE_ARRIVAL, and removal of internal keys from poll payloads.
…ed pages Update configuration, key/value maps, overview and use cases, which stated that poll delivery applies no JSONata transform.
Describe event_filter as a general outbound use case setting: input, bindings, result, error handling, save-time validation, and which deliveries it applies to. Link it from the poll payload contract.
… backend behaviour Late arrivals are measured against everything already leased, carry no envelope marker and are signalled only by MSG_LATE_ARRIVAL. A rare lease race can deliver one event under two message ids, so consumers should deduplicate on use_case_id plus event_id.
…ehaviour Deduplicate by event_id, count expired leases toward the late-arrival watermark, and state that internal keys are stripped before storage and before the payload mapping runs.
…ture behaviour Document the preview endpoint's 400/404 rules, the required event_catalog_event with event_id, the 500 ms and depth guardrails, enqueue-time re-validation, the mapping_error format, zero delivery attempts on failed-mapping dead letters, and the fix, unblock, redrive recovery workflow.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Documents the poll delivery JSONata transform and the pollable outbound hardening (integration-toolkit-api !242 and !243).
What
pollable-outbound.md:mapping_version, failure handling perpoison_policy, redrive withreapply_mapping, the preview endpoint, and a multi-org middleware example using key/value mapsorg_id,mapping_version) and DLQ/redrive field updatesuse_case_id+event_idconfiguration.md:jsonata_expressionfor pollkey-value-maps.md,overview.mdanduse-cases.md.monitoring/codes.mdis generated. Regenerate it withnpm run update-monitoring-codesafter the backend MRs merge.Verification
npm run buildpasses (onBrokenLinks: 'throw'), with no broken links or anchors.Merge once the backend MRs are released.
🤖 Generated with Claude Code