#ab110_connect-account-onboarding
violet sealBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always 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/1469006629746900992
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- ab110_api, 21 minutes ago, 3 messages
magic crow
Apologies for the frustration. Our threads here aren't equivalent to support tickets, and they aren't meant to be long-lived. I didn't get a response for a while and closed the thread as we do here.
Can you elaborate more on what is happening here? Is the request ID you shared from after you took remedial actions?
worn cargo
If that's the case, then perhaps your support team shouldn't send people here. And for the record, my ticket was open for less than 20 mins.
The request ID I shared is from after I took remedial actions. I received an email regarding the suspicious activity and prompted me to verify, which. I did.
magic crow
They aren't supposed to direct people here 😄
That request is an idempotent request, so it's expected to return the same response as the previous request that used that idempotency key. If you make a net-new request, does the error persist?
worn cargo
I am trying to start the onboarding session from our site's page. We have a button to trigger this, but it seems like all my requests share the same idempotency key. Not sure how to test a net new request unless from backend?
magic crow
I'm not sure either without substantially more context on your integration. That being said, it sounds like idempotent requests may not be implemented correctly in your flows. They aren't intended for retrying requests that threw an error, instead they're designed to be able to safely make a request a second time without risking duplicate actions being taken so you can recover from networking failures.
worn cargo
Okay that makes sense. I will do some research, this part was implemented a while ago before I came on to the project so I'll have to check how those are being handled and if we can do it better. Thank you!
magic crow
Any time! And sorry again for the routing confusions
worn cargo
No problem, it just feels bad being bounced around but I appreciate the help regardless. Hope you have a great day!
magic crow
You too!
violet sealBOT