#abdurrehman_webhooks
1 messages ยท Page 1 of 1 (latest)
๐ 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/1444998010957467751
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
๐ happy to help
hello hi there
would you mind sharing the webhook endpoint's ID? we_xxx
yeah sure . btw its really annoying :/
what is?
this issue. well here is the old one that is kind of still active https://dev.joinmycorner.com/api/v1/stripe/subscription-processing/
this is now being replaced by this https://dev.joinmycorner.com/api/v1/webhook-events/stripe/subscription-processing/ .and this destination is not pickup events as suppose to
can u share why is this happening ??? and any possible workarounds???
what's your account ID?
you need to disactivate it on your dashboard
u mean the webhook right???
yes
but i had already removed/deleted this one https://dev.joinmycorner.com/api/v1/stripe/subscription-processing/ since many days, its only like 1 hr ago created again to confirm my theory
what is your theory?
that stripe is still routing events to this https://dev.joinmycorner.com/api/v1/stripe/subscription-processing rather than pointing to this destination https://dev.joinmycorner.com/api/v1/webhook-events/stripe/subscription-processing/
btw i have disabled corner-old
which event you think was misrouted?
all of these. like subscription created
I cant get any single event to this corner-vibrant destination
evt_xxx
it's sending to the right webhook endpoint
but it's failing with this error:
{"error": "Failed to create stripe subscription", "message": "'NoneType' object has no attribute 'split'"}
so basically there's an issue on your side
but i triggered that event through resend button .But what i need is that stripe should trigger this via flow
its not about this webhook implementation i think. customer.subscription.created was being triggerd before during the flow
it's still
but now as i have mentioned earlier . after i had updated the routes stripe is not triggering this
it's still being triggered as I explained
but it's failing on your end
so you need to debug your code to see why the error I shared earlier is happening
its only triggered by clicking the RESEND button
if it was then I would see it as a retry, which is not the case
yeah i had debugged that
ok now i am creating subscription right now
u can see urself if new logs appears or not
no new events logged
as u cans ee
see*
@atomic brook kindly share ur thoughts
taking over here, and struggling to understand the actual issue. can you summarise?
the issue is that corner-vibrant webhook is not responding to stripe events
is this the ID we_1SYR3FPqwSINQbc38OmNbOza?
as compared to corner-old which when activated respond to events .but its not suppose to
yeah
I think my colleague already explained this right? your endpoint code is throwing an error:
{"error": "Failed to create stripe subscription", "message": "'NoneType' object has no attribute 'split'"}
its not responding to any stripe event
hmm yeah but its only internal implementation .Main problem is that i have trigged subscription created event which is not handled by this
well, it is. that error I just shared is thrown by your endpoint when it receives a customer.subscription.created event: https://dashboard.stripe.com/test/events/evt_1SYRa4PqwSINQbc3gx7xSLui
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
you can see all of this in your Dashboard
since 28th i have tried to trigger this destination via multiple tries but its not triggerd
there was 3 delivery attempts of evt_1SYRa4PqwSINQbc3gx7xSLui on the 28th โ all failed with the error I shared
you need to debug where/why that error is being thrown in your code
I don't know what 'refresh my webhook destination' means
let say if i have this https://dev.joinmycorner.com/api/v1/stripe/subscription-processing/ route and now i want stripe to point to this updated one https://dev.joinmycorner.com/api/v1/webhook-events/stripe/subscription-processing/
what can be the process for this
looks like you have an endpoint for
https://dev.joinmycorner.com/api/v1/webhook-events/stripe/connected-accounts/ already, right? but you've set it up as a Connect endpoint. was that intentional?
yeah I did . its a separate route for handling connected accounts
but only main thing i need right now is stripe to point to corner-vibrant instead of corner-old
that's not how this works. we don't 'point' anywhere โ we send all events that fire to all webhooks endpoints configured to receive them
if you want to stop one endpoint from receiving new events, then just disable it
right now there's 3 endpoints on your account:
- https://dev.joinmycorner.com/api/v1/stripe/subscription-processing/ (disabled)
- https://dev.joinmycorner.com/api/v1/webhook-events/stripe/subscription-processing/ (failing)
- https://dev.joinmycorner.com/api/v1/webhook-events/stripe/connected-accounts/
(Connect events)
i had try to create subscriptions right now but i cant see any failing events for https://dev.joinmycorner.com/api/v1/webhook-events/stripe/subscription-processing/
only logs are of till 28th
how are you creating subscriptions?
by checking out to stripe via client app
the requests for Checkout Sessions on your account I see from today are for mode: 'payment' sessions so they wouldn't generate a subscription: https://dashboard.stripe.com/acct_1RGxF0PqwSINQbc3/test/logs/req_GdG5xxjrU9kSh3
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
yeah i got it. the checkout session is in fact not being found due to which this destination is not being reached at all
i think i am wrong in debugging this issue
let us know if we can help any further