#N0xB0DY - webhooks
1 messages · Page 1 of 1 (latest)
Sure,
here :
"evt_1KTlg1QeJ5Exiw7eUxVUCpne"
and here:
"evt_1KThO5QeJ5Exiw7eNcmWUt90"
and many others
Here's what I'm doing in ASP:
First I receive and validate the hook
Gotcha. I'd need to see your webhook handler code. Something is weird there
Here is the validation process
Then It's switched to it's corresponding handler
This is the where I handle session completed:
What exception are you getting?
it first checks if the session is paid, then check if the gift card status is not updated from manually redirecting the client
And do you know where in your code is throwing it?
As for the second event I sent, it was after saving changes, which I know was my fault because I had the wrong operator
But even after I removed it, I received a different error, as in this:
"evt_1KTkfaQeJ5Exiw7eeWINLYbN"
Is it possible that stripe is not allowing me to check the same session info while occupied with another process?
I thought the request hit timeout, but I don't see that anywhere in the errors I received, so I'm sure this is not the issue.
It is hard to say because I don't know much about the error itself. Have you debugged and stepped through what happens in your code when the exception is thrown?
Like which line of your server code is throwing an exception, and can you send the full text of the exception? That 500 error is what your server is sending in response to this exception, but it doesn't say anything about the exception itself
I'll rewrite it to contain the exception, it's deployed so I can't debug it.
It was working fine locally though
Ah gotcha, sorry to hear that is rough to not have that info.
Here is a new event: "evt_1KTq9aQeJ5Exiw7e2pN9Eie1"
This is weird, I resent it manually and it's fine.
Interesting. So this is with the new exception containing code you added?
yup, it says it's null
Do you have code you can add to get a better idea of which object is null?
Yes, I did, and it turned out that it's my fault. Thanks for the help.
Still don't know how it returned success the other times, it was never supposed to be success with the error I got.
Interesting. Great job nailing down the issue!