#mandiocapy
ember cape
paper gulch
Hi there 👋 is the event handling code that is running on your endpoint responding to us with a status in the 2XX range promptly once it has confirmed the validity of the event's contents (and before doing any heavy processing tasks like writing to a database)?
nocturne oasis
"statusCode": 400,
"reason": "MISSING_INFO",
"message": "Zap is missing a thing, please select a zap thing to continue!",
"args": {
"bubble_code": "1678714913943x472373677012920960"
I am using Bubble for this app. To my knowledge, it doesnt send any info back. It does every subsequent action locally
Is there a way to shut down that event or something?
paper gulch
I'm not familiar with the Bubble framework, so I don't know exactly how to build a functioning webhook endpoint with it.
A key step to our webhook event flow is to provide us with a response in the 2XX range to indicate that your endpoint successfully received the event, otherwise we assume it was not delivered successfully and queue it to be resent:
https://stripe.com/docs/webhooks#acknowledge-events-immediately
Where is that error message you shared being surfaced? Is that thrown when your endpoint tries to interact with another service?
nocturne oasis
I was testing it on live mode yesterday and got it to work on the last payment. But for some reason Stripe still keeps trying to send some events
paper gulch
Can you share the ID of an Event where you're seeing that behavior?
nocturne oasis
"id": "evt_1Ml1gMF29ffnq1lzdQIjK84J",
This was the last live payment we made and got the data on our app and everything worked
But for Stripe, it didnt
My app recorded the payment as paid, the date 03/13/2023 12:04 am and the charge ID succesfully cs_live_a16LgR77siB5THhuYvCGcFPNKRiZQAuRwuZAAqMDoajMWfPAEIVoCtrRA0
paper gulch
Most of the attempts to deliver that event were met with 400 responses from your server (the 1 exception to that is when it was delivered to a different endpoint), so it is expected for us to continue trying to resend the event because we didn't get an indication that it was successfully delivered.
Is your code crashing? What is raising that MISSING_INFO error that is being thrown back to us?
nocturne oasis
Its not crashing. Dont know what that is
It says its a Zap thing, but checked the Zaps linked to it and nothing is missing
Which endpoint does it tell you worked??
paper gulch
One related to a Connect Platform that your account seems to be connected to, you can view that information in your Stripe dashboard:
https://dashboard.stripe.com/events/evt_1Ml1gMF29ffnq1lzdQIjK84J
nocturne oasis
Checked that. Doesnt display any missing info
It even says it displays the payments as being done
paper gulch
Webhook events do not relate to completing the payment.
nocturne oasis
Resent the events and my app keeps getting the data correctly
paper gulch
Then you need to diagnose why your app is not responding to us with a status in the 2XX range.
nocturne oasis
What is the 2xx range
paper gulch
It is the range of successful response status codes for HTTP requests. 200 is the most common one used.
Right now you're server is responding to us with a 400 status code, which is an indication that the request was not successful:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
We don't have insight into the inner workings of your event handling code, so we aren't sure where the problem is. What we can tell is that when we send a request to your server, it responds to us with a 400 status code indicating that it could not receive the event that we tried to deliver so we queue the event to be resent.
My suspicion is that your event handling code is ingesting the event's contents, then trying to reach out to to other systems to trigger processes and one of those is failing. You will want to add logging to your endpoint (or an equivalent debug approach for the Bubble framework) to see where your code stops behaving the way you're expecting.
nocturne oasis
This is the API connector
Is that checkbox "Return a 200 if condition is not met" probably what youre talking about?
paper gulch
I'm not sure, I'm not familiar with the Bubble framework or how its settings impact its behavior.
nocturne oasis
Ok, gonna test every single variable change then
paper gulch
That's one way to go about it, but Bubble seems to have docs for their settings. Based on this it does sound like toggling that one on will cause your endpoint to respond with a 200 if a condition is not met, though I'm not clear on what that condition is or when it is evaluated.
https://manual.bubble.io/core-resources/api/the-bubble-api/the-workflow-api#return-a-200-if-condition-is-not-met
nocturne oasis
Shit! That was it
Toby you the GOAT!
Thanks for helping a no-code idiot hahahaha
paper gulch
Haha, rest assured I will never refer to you in that way. I'm always happy to help and glad you were able to get to the bottom of it!
nocturne oasis
hahahaha