#fijvect
worthy glade
lethal matrix
hello! can you share both request ids [0]? it'd look like req_xxx
lethal matrix
the successful one too would be great
blazing basin
It's a bit harder to find the successful one since it doesn't show up in the logs, haha. I'm still trying to get it, sorry
lethal matrix
you can find it in the response header : https://stripe.com/docs/api/request_ids, you can see an example of how to get for the relevant library on the right
blazing basin
ok
Here is a new failed one I just did: req_HCDr4g48OfZGoB
And the corresponding refreshed attempt that worked right after: req_m6dzc9rbsJczd3
lethal matrix
those are two entirely different API endpoints. https://dashboard.stripe.com/test/logs/req_HCDr4g48OfZGoB - for the one that failed, you passed in an Invoice id into the payment_intent parameter
a PaymentIntent id starts with the prefix pi_
hmmm
blazing basin
Interesting, ok that might be a starting point for me to look into where in my code it might be branching unintentionally then.
lethal matrix
onesec, i may have opened the wrong request id
oh nvm, the requests that i opened are correct
blazing basin
I think I may have just spotted where it might be branching! Sorry, thanks for setting me on the right track, haha.
So i should be good now! If I have any issues once I fix what I'm seeing here I'll open a new ticket. Thanks again! 🙂
lethal matrix
you're welcome! glad i could help!