#scif_unexpected

1 messages · Page 1 of 1 (latest)

naive deltaBOT
#

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

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

digital crane
#

Hello, we don't save successful GET responses so can you share the full response for what you received in the request?

bright leaf
timid bough
#

hi @bright leaf , its due to the same issue. You're making the request too fast. The GET call was made at
2025-05-26 05:50:26 UTC, which is the same time the invoice object is created.

bright leaf
#

Sorry but this is outrageous behavior

#

If your backend doesn't have data — please let us know about it

timid bough
#

As recommended by alex on the previous thread, please wait for the checkout.session.completed event, which was emitted at 2025-05-26 05:50:27

bright leaf
#

FAil the request, mark it with a proper status

#

Or whatever else, but not serve data which is marked as full/competed/valid in the shape of inconsistent objects

#

I admit your point, it could be the case that data is not available but in this case the status of an object (checkout session) must be appropriate

#

Otherwise you are producing invalid and inconsistent code claiming it's as complete

timid bough
#

I understand your frustration with this limitation, but as Alex mentioned earlier, the best workaround now in this case for the current API behavior requires waiting for the checkout.session.completed event to retrieve the Invoice ID. Unfortunately, there isn't a more efficient workaround available in the current implementation.

bright leaf
#

Yep, I'm reworking my code now but I'd appreciate if you would lodge this as a bug report. Serving of inconsistent data and moreover wrong types is actually a bug.

digital crane
#

It'll be better if you write in yourself. It means little if I raise the feedback since I don't know who you are, if you write in to support then you're authenticated and the feedback is raised on your behalf so we can get a better sense of impact, we can track it and let you know directly if something changes or if we need more input and so on.