#mason-terry_webhooks

1 messages ¡ Page 1 of 1 (latest)

tired hillBOT
#

👋 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/1346566197390475316

📝 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.

fading briar
#

hello! i think it's 30? let me double check that

#

we don't generally support the dashboard, is it even possible to resend them from there? i actually have never tried that

#

but i would be very surprised if we had a different limit there

rotund root
#

Yes we have manually done that before from the dashboard. We don't do it often, but we have seen a limit I believe. I just wanted to make sure because we have to put in a code fix and want to make sure we don't run out of time to resend the event.

fading briar
#

ok cool! yep 30 is how long we retain the data on our end too, so that should be consistent among all methods. and worst case if for some bizarre reason the dashboard is more draconian, you can always use the CLI