#jbwyme_error

1 messages ¡ Page 1 of 1 (latest)

hollow hornetBOT
brave jungleBOT
#

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

hollow hornetBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1248067363342127164

📝 Have more to share? Add details, code, screenshots, videos, etc. below.

hollow imp
#

Request id of failing transfer: req_EjIatVv44c2Ehr

Request id of active features: req_jGLQK8ujDLNJeh

You can see inbound_transfers.ach.same_day is active

sharp mist
#

Hi @hollow imp let me take a look

#

Ok, so req_EjIatVv44c2Ehr is replay of a previous request: req_C8DbbHyxPK1RbJ because you used the same Idempotency key, and req_C8DbbHyxPK1RbJ was created at 2024-06-05 23:59:14 UTC, which is before req_jGLQK8ujDLNJeh

#

You might want to try again with a different Idempotency key

hollow imp
#

Ah ok I will try that, thanks!

hollow imp
#

yep that fixed it, thanks again