#fredyfx_unexpected
civic sirenBOT
đ 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/1324476535591145482
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
blazing carbon
I'm using Staging Server.
I have a table with a column that contains StripeSubscriptionId
The value is: sub_1QDHmDDex10DcNY8bDn31mHA
That value EXISTS on my Stripe Dashboard.
odd glen
Hello, I am not quite understanding your issue in Stripe terms. Can you tell me more about what your system looks at in Stripe to determine if a member is active and what is missing?
blazing carbon
Hi Pompey, good afternoon. Happy new year! Thanks for helping me
I have code that checks if a user has an active membership: (Active or Trial) are valid options
I have 2 user's accounts on my system that were working nicely. This morning a user reported that my system was not working.
I checked it and It didn't work.
I double check on the Stripe Dashboard. I saw the Subscriptions Active. Both users are there with active tag
On my backend, when I arrive to check the Membership Status, it throws an error:
An error occurred while checking the subscription status. for userId: <GUID>
Jan 02 20:34:43 localhost dotnet-project-api-staging[1747060]: Stripe.StripeException: No such subscription: 'sub_1QDHmDDex10DcNY8bDn31mHA'
odd glen
Gotcha, do you happen to have a request ID (req_123) that is assosciated with that lookup failure? I can find it in logs otherwise but it can be easier if you have it on hand
blazing carbon
One moment, let me check
I found the real problem!!!!
At some point, the system recorded two times a subscription but only 1 got paid. The other was deleted. Because of it, now, it throws an error.
Thanks for the patience
Layer 8 error.
odd glen
Gotcha, glad you were able to spot the issue!