DiscordStatus
Guias / Guides

How to Reactivate an Interrupted Queue

Asaas automatically interrupts a Webhook queue after 15 consecutive failures when delivering notifications.

When this happens, new events continue to be generated, but they are no longer delivered until the queue is reactivated.

Therefore, before restoring synchronization, it is essential to identify and fix the root cause of the problem.

Impact of an interrupted queue

When a queue is interrupted:

  • new events continue to be generated normally;
  • events stop being delivered to the application;
  • synchronization between systems is interrupted;
  • charges, payments, subscriptions, and other resources may stop being updated in the integrated system;
  • events stored for more than 14 days are permanently deleted.
🚧

Attention

Reactivating the queue without fixing the underlying issue will cause it to be interrupted again after new consecutive failures.

Step 1: Check the Webhook logs

Before reactivating the queue, inspect the logs to identify the error.

See:

How to view Webhook Logs

The logs allow you to verify:

  • returned HTTP status code;
  • payload sent;
  • timestamp of the attempt;
  • number of retries;
  • error message received by Asaas.

Step 2: Fix the issue in your application

After identifying the root cause, correct the endpoint behavior.

The most common causes are:

  • incorrect URL;
  • processing timeout;
  • internal application error;
  • firewall blocking Asaas IP addresses;
  • HTTP response different from 200;
  • server unavailability;
  • validations rejecting the received payload.

If necessary, consult:

  • Paused queue;
  • Error 400 (Bad Request);
  • Error 403 (Forbidden);
  • Error 404 (Not Found);
  • Error 408 (Read Timed Out);
  • Error 500 (Internal Server Error);
  • Connect Timed Out errors;
  • Other errors.
🚧

Important

The queue should only be reactivated after the issue has been fixed, ensuring that the application is ready to receive new events.

Step 3: Reactivating through the web application

After fixing the issue, go to:

User Menu → Integrations → Webhooks

Locate the interrupted configuration and reactivate the queue.

Reactivating via API

You can also reactivate the queue programmatically by updating the Webhook configuration.

Simply send the following attribute:

{
  "interrupted": false
}

Use the Webhook update endpoint.

See the complete endpoint reference:

Update Webhook

Recovery flow example

Consecutive failures
↓
Queue interrupted
↓
Check logs
↓
Identify the issue
↓
Fix the application
↓
Reactivate the queue
↓
Queued events are resent
↓
Synchronization restored

Best practices

📘

Recommended

  • Monitor Webhook logs regularly.
  • Implement idempotency to support retries.
  • Process events asynchronously.
  • Ensure your endpoint responds quickly.
  • Always return HTTP 200 after processing the event.
  • Verify that your firewall is not blocking Asaas IP addresses.
  • Never reactivate the queue without first fixing the root cause.

📌

Important

If you have just created a new Webhook and it already appears as interrupted, verify that the synchronization queue for that configuration is active.

Next steps

After reactivating the queue, we recommend reading: