#dtc-_webhooks
radiant ventureBOT
👋 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/1410913376871387317
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
pearl grail
Can you confirm what behaviour exactly is unexpected?
You mean the redirect is ~immediate and we don't wait for the 2xx from your local webhook?
If so that is expected – the 10 second 'delay' is only observed for non-CLI endpoints
shell marten
@pearl grail Thank you very much for your detailed explanation.
Your answer matches exactly what I intended to ask.
I now understand that the behavior I observed was due to working in a CLI environment, which is why the 10-second delay was not reproduced.
pearl grail
Yep, if you setup a non-CLI endpoint then we'll respect the ~10 second delay whilst your webhook acknowledges the event. It's just not supported with the CLI today because of how it's built
shell marten
@pearl grail Thank you very much for your help.
I will try again using a non-CLI endpoint.
You can close this question. Thanks again!