#mangle_webhooks
1 messages ยท Page 1 of 1 (latest)
๐ 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/1400190300734881984
๐ 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.
- mangle_api, 1 day ago, 7 messages
- mangle_invoice-payment-intent-relationship, 1 day ago, 28 messages
- mangle_invoice-proration-credits, 1 day ago, 69 messages
You here?
Hi there ๐ it was deleted because it was part of a Test Clock that got deleted, so the objects inside the Test Clock were also cleaned up.
Related Event: https://dashboard.stripe.com/test/events/evt_1RqUy2DmVlmqORBIaC5zjaEJ
Test Clocks are automatically deleted after 30 days:
https://docs.stripe.com/billing/testing/test-clocks/api-advanced-usage#delete-clock
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
oh.. so i won't have issues on production
can you restore the user without test clock please?
Correct, this behavior should not be seen in livemode. Unfortunately, no, those deleted Customers can't be restored. In general, objects inside of a Test Clock aren't really usable outside of that Test Clock simulation, because they get associated with a fake system clock and get out of sync with the rest of the things going on outside of the Test Clock.
Out of sync isn't the best choice of words there, but I hope it's clear what I mean. Happy to try to clarify if not
aa okay, because locally i didn't had the webhook listen so i have leftovers in my database, i will delete them manually in cascade then.
I'm happy that is testclock deleted, thought it was a bug on my end. Glad the production is safe. Thank you