Discussions

We’re making two changes to Provision Task webhooks that will affect how often you receive events and which action value you see. If you subscribe to Provision Task webhooks, please review the details below.

1. Fewer false status events

Today, when a provision task is updated without its status changing (for example, a date or field change), you can receive a repeat COMPLETED, ERROR or READY webhook for a task that is already in that status. We’re fixing this so the action reflects what actually happened.

What you’ll notice:

Updates that don’t change the status will arrive with the UPDATE action instead of COMPLETED, ERROR or READY.
Real status changes behave exactly as they do today.
The payload shape is unchanged.
Right after release, each active task may send one last repeated status event on its next update. After that, the behavior is as described above.

If your integration treats every COMPLETED, ERROR or READY webhook as a new status change, you’ll see fewer duplicates. If you currently rely on those duplicates, for example to catch field changes, subscribe to the UPDATE action as well.

2. New Provision Task Ready events

Tasks that move from RapWaiting or RapDelayed back to Ready will now send a READY webhook. Previously these transitions sent nothing.

What you’ll notice:

If you subscribe to READY, expect a significant increase in volume, potentially thousands of events per day across the marketplace. [Renewal tasks cycle through this state roughly every 8 hours, so the same task can send READY several times a day. / This applies to non-renewal tasks only.]
Each event carries the task’s current status (Ready) and the previous status in the payload.

What we recommend

Make sure your endpoint can handle higher READY volume, and that your processing is idempotent.
Use the status and previous status in the payload rather than the action alone if your logic depends on a specific transition.
Review your webhook action filters to confirm they still match the events you want.

Questions or issues? Reply in this thread or contact [email protected].