#sg_webhooks-bug
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/1288541076352794721
๐ 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.
- sg_plugin-sources, 1 day ago, 73 messages
- sg-pushpaveni_webhooks, 2 days ago, 23 messages
- sg-pushpaveni_webhooks, 5 days ago, 8 messages
kindly support to resolve the issue
Hello! Can you give me the request ID showing that error? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
here is it req_DdeRXpKwTYMfip
Ah, interesting. So you got this error when trying to modify the Webhook Endpoint in your Dashboard? What specific changes did you make in the Dashboard that led to this error?
We usually change the webhook end point URL to our different servers for our development and testing purpose.
we got the error when we change it
it was working even few weeks before also. from last week, we couldn;t able to change the URL because of the error
Im working on the migration process as its mentioned in the mail which we received as below
So the only thing you changed is the URL?
yes
Ah, okay, sounds like this is a bug then. I recommend you write in to support with the details and they can help you further: https://support.stripe.com/contact/email
Happy to help!