#xqprtzcv_subscription-event
1 messages ¡ Page 1 of 1 (latest)
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.
- xqprtzcv_api, 3 days ago, 10 messages
đ 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/1261080265405497436
đ Have more to share? Add details, code, screenshots, videos, etc. below.
Hm, you're making more than just metadata updates to that subscription
Yes, I have a "dummy" subscription for the trial which doesn't require a payment method, and doesn't renew. This is upgrading to a regular subscription.
Okay, so the key here is to note the created time stamp on these events
ah and you're also using test clocks
Give me a few minutes to piece together a timeline
OK, thank you.
Okay, so the event you shared was sent during the real time 2024-07-11 20:59:43 UTC
This happened before the real time of req_NongVADZd9h4Cr (2024-07-11 21:53:53 UTC) so can confidently say it came before you updated the Subscription with trial_end: now
I believe I found a solution in an older message:
It suggests comparing the trial end date with the time that the webhook is sent
xqprtzcv_subscription-event
Thanks for your help, and sorry I sent the incorrect request id.