Webhooks not triggered when for some subscription updates

Products and Orders APIs
1

Hi there! We’ve found that subscription_contracts/update webhooks aren’t always fired when we’re setting the next billing date via subscriptionContractSetNextBillingDate. It’s not consistent because most times we do see the webhooks triggered but not all the time. This inconsistency makes it harder for us to keep data in sync.

We find that if we create a draft, update the draft’s next billing date, then commit the draft that we always see the webhook (even if its delayed) but that’s not the case for the subscriptionContractSetNextBillingDate endpoint.

Any advice or investigation would be much appreciated!!

1 Like
2

Hey @Brian_Singer,

Thanks for sharing this. Do you by chance have a recent example of when you used the subscriptionContractSetNextBillingDate? If you have the request Id I can see what I can find in our logs.

Also, since you mention it’s inconsistent, do you have an idea of approximately how often this happens with this mutation?

3

Sorry for delay - unfortunately we don’t have request IDs but we’re going to try to start logging them so we can in the future.

I can only make a guess. It’s not frequent but when it happens it seems to be in batches. I’m completely guessing about 1-5% of the time.

1 Like
4

Thanks for that. Interesting it seems to happen in batches.

Once you have a specific example request id, share that here and we can take a closer look.