The suite follows incoming provider messages, outgoing customer changes and application event delivery. Acceptance checks the retained identities and visible recovery records across each handoff, rather than treating a successful individual dispatch as proof of the whole chain.
Notification verification determines which downstream events may be dispatched. Consent and connection changes determine subscription eligibility, while repeated work and bounded retries are checked against the retained delivery and recovery history.
The reliance links identify detailed capability scenarios. None of these composed acceptance sequences has a verified executable binding at the pinned revisions; the corresponding coverage finding remains open.
An endpoint, a matching event consumer and an accepted change subscription are available.
Steps
Process a valid provider notification and route its event; separately raise a subscribed business change.
Expected
The notification, routed event and projected subscription delivery each retain their own traceable identity.
Data
Run-owned declarations, records and role fixtures in an isolated workspace.
Source
services-platform:modules/integrations/tests/integration/services/webhooks/webhook-worker.integration.spec.js#rejects a request whose signature does not verify, writing no event,services-platform:modules/integrations/tests/integration/services/subscriptions/subscriptions.integration.spec.js#turns a CRM change event into a queued delivery of the catalog projection, never the row,services-platform:modules/integrations/tests/integration/services/events/event-router.integration.spec.js#records an event every consumer handled or ignored as delivered, to each of them
A subscription and event consumer repeatedly fail.
Steps
Exhaust their delivery and routing attempts, inspect dead records and explicitly resume a failure-paused subscription.
Expected
Failed work remains visible after finite retries and resume restores subscription eligibility.
Data
Run-owned declarations, records and role fixtures in an isolated workspace.
Source
services-platform:modules/integrations/tests/integration/services/subscriptions/subscriptions.integration.spec.js#retries a classified failure with the async backoff and records the delivery dead after six attempts,services-platform:modules/integrations/tests/integration/services/subscriptions/subscriptions.integration.spec.js#pauses a subscription after fifty dead deliveries in a row and tells its administrators once,services-platform:modules/integrations/tests/integration/services/events/event-router.integration.spec.js#records an event every consumer handled or ignored as delivered, to each of them
04Readers cannot use secrets or staff-wide recovery accesspermissionnegativeproposed
A workspace reader and Rhythm operator are available.
Steps
Inspect messages and subscriptions as the reader and request cross-workspace event inspection as each identity.
Expected
Reader answers omit secrets and staff-wide inspection remains restricted to the operator.
Data
Run-owned declarations, records and role fixtures in an isolated workspace.
Source
services-platform:modules/integrations/tests/e2e/reader-access.e2e.spec.js#reads no webhook signing secret in any answer,services-platform:modules/integrations/tests/integration/services/subscriptions/subscriptions.integration.spec.js#refuses a subscription to a type the installation has not accepted, naming the type, and writes nothing,services-platform:modules/integrations/tests/integration/services/events/event-router.integration.spec.js#lists the events nobody took for Rhythm HQ, across tenants
05Duplicate work keeps one delivery identityregressionnegativeproposed