#iamdivyatiwari
lime patrolBOT
Hello! We'll be with you shortly. 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.
- iamdivyatiwari-connection-issues, 5 days ago, 8 messages
summer quiver
Do you have a Request ID for the failed request?
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
summer quiver
Yup, I'm looking now
How did you get that Subscription ID?
Was it returned from a request? If so, which one?
soft cave
from my local db.. we stored those ids when the subscription was created
summer quiver
Ahhh, okay
soft cave
Are those not valid?
summer quiver
Was it a pretty old subscription?
soft cave
no... i checked for latest subscriptions as well
and there also i am getting the same
for the newly created subscription i am able to retreive the value
not sure what's wrong with those past subscriptions
summer quiver
Usually we only see this happen due to the retention policy on test mode events: https://support.stripe.com/questions/test-mode-subscription-data-retention
soft cave
oh, then that makes sense
Thanks for the info!
is there any way
we can bypass this condition on test mode?
by passing some variable
summer quiver
Unfortunately not. Usually when you're testing you would want to use Test Clocks to simulate the passing of time, that way you don't run into retention policy issues
