#bwurtz999
1 messages · Page 1 of 1 (latest)
Hi there
Do you see a failed request in your Dashboard associated with that error?
At what part of the process is the error getting thrown?
I'm not sure. This started about 5 or 10 minutes ago
Roughly a dozen readers went offline all at the same time
At different locations
Ah okay actually I see we are looking into this internally
We are working on it
Sorry for the inconvenience here
Nothing you can do, we are working to resolve ASAP
I can let you know as soon as resolved. Hopefully soon
OK thank you. Will you respond in this thread?
Yep I'll tag you here
thanks
@strong walrus I have some more errors to report. I have been using a reader at one of my locations that is now no longer showing up for that location (API or Dashboard)
tml_EsJgMwM1AYKALv
Had one reader associated and now shows nothing
Likely related to the same issue
Think we are having issues with discovery at the moment as well
We are working as quickly as we can to resolve
Thanks. Just wanted to report the new behavior
Yep appreciate it
I believe this should be fixed now @stable stone . What are you seeing on your end?
Yes!
We are back up
Is there anything I can do to prevent this in the future? Was it something about my integration? Or was this affecting other accounts as well?
@strong walrus
Hi, bismarck needed to step away and I'm taking over.
This was an interval error and as hard as we try not to see this, it can happen...in these cases, we have a resources for error handling: https://stripe.com/docs/error-handling.
Got it thanks