Deliver subscribed Rhythm changes to an integration
What It Does
Subscriptions project allowed Rhythm change fields into deliveries for an installed adapter. Push processing invokes the adapter; pull processing waits for a cursor. Repeated dead delivery pauses future fan-out until an administrator intervenes.
The Flow
When Something Fails
The source stream repeats unsuccessful work. The source retains changes awaiting acknowledgement. Return event-specific failures for source retry. Previously successful event processing need not roll back with another failed event. Retain unpublished work for a later pass. Duplicate queue messages can follow publication-before-deletion failures. Retry classified failures with backoff until dead. The adapter can apply a change whose acknowledgement was lost. Log notice failure. New changes are skipped while paused and are not recovered automatically on resume. Reject adapters outside the authorized account boundary. Unread pending changes remain until a valid cursor write. Reject invalid windows or unsupported retry requests. Replay can repeat a change already applied; it does not invent deliveries skipped during a pause.
Open Design Questions
Replay covers existing delivery records and cannot recreate changes skipped while paused. Pull support must remain distinct from unbuilt synchronization profiles.