RabbitMQ holds several queues for each push/pull BSS object. One for the creation of the object and one for the update of an existing object. Each time a sync is initiated, a “sync queue” is responsible for keeping track of the API calls. If something erroneous occurs during a specific period of time, then an automatic notification alert is dispatched to the BSS Admin user.

Let’s examine one such example in the following two sections of this page, where in the first one, you can witness the initiation of the API push/create call, while on the other, you can witness the error handling along with the notification dispatch.

View of Queues in Rabbit MQ

In the following example, we attempt to push/create a BSS account via the API tester. Therefore, the object utilizes the generic “SyncQueue” where it searches the account in the BSS database and performs the “push/create” API call.

Open

By design, the policy for all packages in BSS is 5 attempts to sync an object by 20” intervals.

The following example is the view of an attempt to push an account via the API tester by utilizing the generic “IntegrationSyncQueue”.

Open

By continuing to the below section of this page, you can better understand how the errors are being handled.

Error handling and Alert notification

In case all 5 retries fail, then the failed object is returned to a new queue that is automatically created per error category. In this case, for this error, RabbitMQ created “IntegrationSyncQueue_error“(as displayed in the previous section’s screenshot), and once the item is added to the queue, the alert mechanism is triggered, and therefore an e-mail is automatically dispatched to notify the predefined BSS Admin user with the respective error response.

Example for failed Account:

Table of Contents