Webhook delivery attempt display issue

API Support Transfers
1

Hi,

I was investigating the webhook (188e4209-17cc-4358-ad3c-5049d1c12860) on a failed transfer, and found the following expected behavior:

displayed:

  • 07/07/2022 at 5:47 amHTTPS Status Code: 500 - Internal Server Error
  • 07/07/2022 at 8:15 amHTTPS Status Code: 200 - OK
  • 07/07/2022 at 6:47 amHTTPS Status Code: 500 - Internal Server Error
  • 07/07/2022 at 6:02 amHTTPS Status Code: 500 - Internal Server Error
  • 07/07/2022 at 8:15 amHTTPS Status Code: 500 - Internal Server Error

expected:

  • 07/07/2022 at 5:47 amHTTPS Status Code: 500 - Internal Server Error
  • 07/07/2022 at 6:47 amHTTPS Status Code: 500 - Internal Server Error
  • 07/07/2022 at 6:02 amHTTPS Status Code: 500 - Internal Server Error
  • 07/07/2022 at 8:15 amHTTPS Status Code: 200 - OK

on the webhook fired at 8:15 am, I was able to confirm from my application log that 200 was returned. I’m not sure why would the Dwolla website shows another 500 returns from the same time, and somehow, was displayed out-of-order.

thank you in advance,

Meng

webhook
webhook323×775 43 KB

2

Hi @meng – thanks for reporting with such detailed information!

This is a known issue which we have noted in our backlog and will be picked up based on priority. In the meantime, we recommend referring to the API for looking up the attempts if you’re looking to automate it. Otherwise, the Dashboard is also good to manually reference keeping in mind that the attempts may not be displayed in order causing the overall status to appear as “failed” even though it succeeded eventually.

1 Like