#ross_webhooks

1 messages · Page 1 of 1 (latest)

lunar canyonBOT
#

👋 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/1382416352823738388

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

fickle belfry
#

Hi, taking a look.

#

Where do you see 'can only be configured on a single webhook at a time'?

wooden ledge
#

When I try to create a new event destination with the target API version:

#

This is from the developers dashboard workbench -> webhooks

fickle belfry
#

Yeap, testing it on my end too.

#

Yeah, I can't think of a way around it. I'm talking to a teammate to see if they have ideas. Thank you for your patience.

wooden ledge
#

Ok, sounds good 👍

fickle belfry
#

My teammate was able to confirm that there is not a graceful way of handling this except using https://docs.stripe.com/issuing/controls/real-time-authorizations#autopilot

Autopilot provides fallback options that allow you to continue making real-time authorization decisions when your systems are down, don’t respond to an authorization request, or provide an invalid response.

You'd need to click on the 'contact support' link and work with Support as we are unable to assist with Private preview functionalities in this channel.

wooden ledge
#

Got it, ok thanks for the info! Will this type of upgrade be supported in the future or is the intention that we should look to use tools like Autopilot for "planned maintenance downtime" when we perform an upgrade on our auth request webhook?

fickle belfry
#

I will share your feedback with the product owning teams for future product reiterations. As of now, it looks like the only way.

wooden ledge
#

All right, thanks! I appreciate your time looking into this. Feel free to close the thread. Have a good one!

fickle belfry
#

Sure, you as well