#lukas.giniotis-invoice-finalized

1 messages · Page 1 of 1 (latest)

novel pollen
#

Hi there 👋 I do see from the screenshot that it took 3 days for that invoice to finalize. Do you happen to have a webhook endpoint setup that is listening to invoice.created events?

near dirge
#

Hi, yes we have a webhook that is listening to invoice.created event.

novel pollen
#

Gotcha, so, since you're listening to those events, our system is designed to assume that your process needs to be aware of an invoice being created and because we aren't exactly sure why those events are being listened to we assume that it's because the invoice may need to be updated before finalization.

So, if we stop receiving acknowledgement that those events are being received successfully by your server, then we'll postpone the finalization of the invoice until your system acknowledges receipt of the invoice.created events or we've fully exhausted the event retry logic (about 72 hours).

#

This behavior does exist in both test and live mode, so it could add a delay to the finalization flow if those events stop being received successfully.

near dirge
#

Thanks a lot for the in-depth answer. A follow up question then - we have four non-Prod environments, thus four webhooks listening to the same event. Do they all need to respond with 2xx for it to be considered acknowledged? I can see that for this particular event, three webhooks succeeded, but one failed.

novel pollen
#

Yup, any delivery failure is seen as a reason to postpone the finalization, and all listening endpoints will need to respond successfully.

near dirge
#

Got it. Thanks a lot!

novel pollen
#

Any time!