[Production] Elevated API Errors Creating New Transfers

Update timeline

1. investigating Mar 21, 2025, 09:32 PM UTC

   Beginning 03/21/2025 04:09 PM CT, we began experiencing an elevated level of API errors on the creation of new Transfers in the Dwolla API. Our engineering team is actively investigating the cause and working towards a resolution. We apologize for the inconvenience and will provide an update shortly.

2. monitoring Mar 21, 2025, 09:50 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Mar 21, 2025, 10:24 PM UTC

   We have resolved the issue causing elevated API error rates and 500 errors that began at approximately 4:09 PM CT. Some transfer requests during this period resulted in a 500 status code. For clients using idempotency-keys, retrying these requests might initially return a ‘409 Conflict’ error. This is due to Dwolla’s 24-hour idempotency key lock. To ensure your transfers were processed correctly: 1. Check the Dashboard/API: Verify if the affected transfers were successfully created. If they weren’t, proceed to the next step. 2. Retry with a New Idempotency Key: If the original request resulted in a 500 and subsequently a 409, retry the request using a new idempotency key. This is the recommended approach. 3. Retry with Original Idempotency Key (After 24 Hours): Alternatively, you can retry the original request (with the same idempotency key) after the 24-hour lock expires. This will eventually return a ‘201 Created’ response if the transfer was ultimately successful. If you continue to experience issues or have any further questions, please reach out to us at [email protected]. We apologize for the inconvenience.