The code performs the following steps to trigger the webhook:
 

Webhook (no retry) > Webhooks::Worker (no retry) > Webhooks::RecordWorker > Webhooks::RecordWorkerRetry (in case of retry in the RecordWorker)

Webhook receives action performed by the card , repo id and optional info . It checks if the action performed by the card is the type of action that will trigger a webhook. If it is it will call the second step.

Webhooks::Worker > receives action performed by the card , repo id and optional info. It finds the webhook id and if the id exists calls the third step.

Webhooks::RecordWorker >  receives webhook id , repo id and optional info. It attempts to trigger Webhooks::Notifier, which is the one that will actually do the webhook thing.

If our system has any issues during this action it will then proceed to the last step. Otherwise, it will finish the action.
*Problems on your server are not triggering the retry functionality. 

  Problems on the client side include timeouts which are determined by the env var WEBHOOKS_NOTIFIER_TIMEOUT (CURRENTLY SET TO 10S)

Webhooks::RecordWorkerRetry > same as last step but keeps retrying for at least 10 times.