#piercy_api

1 messages ¡ Page 1 of 1 (latest)

unreal kiteBOT
#

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

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

hasty igloo
#

hi there - can you share the IDs of any events (evt_xxxx) or webhook endpoints (we_xxxx) that are being affected by an issue with thin events?

full yarrow
#

acct_1DW87gDRH1nN3Sur
acct_1Gin94DD3nZJlvMp

There is no issue, except that I need to create new endpoints, and I can't because I have to provide thin endpoints.. but we have no thin endpoints

#

We only use snapshot endpoints, not thin ones, so i cannot get passed the screen

hasty igloo
#

are you getting an error when trying to set up an endpoint/destination in your dashboard?

full yarrow
#

No but the screen is unskippable

hasty igloo
#

can you share a screenshot please?

full yarrow
#

Continue is greyed out, so I cannot continue without entering a value, but I cannot enter a value as we do not use thin endpoints.

hasty igloo
#

so this means that in your 'Selected events' you've selected some types which are thin events, which is why you're being prompted to add a destination for these

#

is there a specific list of event types that you need to listen for, or are you selecting all?

full yarrow
#

Im selecting all

hasty igloo
#

since that includes thin events, you won't be able to bypass this screen while including these in your selected events

full yarrow
#

That documentation lists 3 events, I can only find two of them (the v2 one doesnt exist) but i still get the problem.

Are the v2.core.health.* events also thin events?

hasty igloo
#

hmm, that list should contain all publicly available v2 events - sorry for the inconvenience!

yes, those are thin events

full yarrow
#

yes that got me past it. Ill email our account manager about this. Blocking a production release at the last moment is a terrible experience. I dont know why this blocking preview feature has been enabled on our account, as far as I am aware no one has asked for it

hasty igloo
#

ok glad to hear that you were able to progress at least - another option would be to disable the 'workbench' UI and go back to the old 'developers' UI which only supports our v1 namespace (if you get blocked by this again)

#

for context though, the v2 namespace is being rolled out and these events are publicly availble, which is why selecting all includes them

full yarrow
#

Honestly, if thats your plan i wouldn't recommend it, you are about to block many people from creating webhooks

#

A production release of our stripe code is a significantly stressful time for us

#

and having a curve ball thrown in at the last moment is not good at all.

hasty igloo
#

yeah if you've had this experience then you're likely not the only one, so I can take this feedback to the team