SEQUENCE GAP

Sequence Gap

All the transactions on a single business unit should come with a Previous-Transaction header, so that it can be made sure that all transactions are present and were processed. The repository service is designed to be able to detect Gaps in the sequences of transactions. When another batch of transactions is received, the repository will check if there were any Gaps in this batch of transactions. If there are Gaps, the repository will wait for them to be healed, but if it does not happen within a certain time, the repository will send out an event notifying customers that a Gap is present.

TRANSACTION REPOSITORY DOES NOT TAKE ANY ACTIONS WHEN THE GAP IS DETECTED EXCEPT FOR SENDING OUT NOTIFICATIONS.

Structure

Each Gap includes only information about the transaction that detected the Gap: tenant id, business unit id, transaction id. The service sends it out using the Sequence Gap Event Source so customers are able to set up a webhook on their side and decide on how they want to process them.