#monove-terminal-issue

1 messages · Page 1 of 1 (latest)

knotty rainBOT
inland sluice
#

Checking in to if we have an ongoing issue here. When about did you start seeing these issues?

#

Also can you tell me more about the issues that you are seeing?

rough shore
#

the same issue i filed with you 3 weeks ago

#

we push payment intents to process_payment_intent and rteceive response that the Reader is offline. meanwhile the payment request actually went through

inland sluice
#

Oh I remember that. And you still have a ticket that I picked up that is related to that right?

rough shore
#

correct with no update

#

its happening every day but we have elevated errors now

#

like a lot

#

multiple locations, multiple devices

inland sluice
#

I apologize, I am normally much more on top of this, let me check/push on the issue I raised here.

rough shore
#

in the past 20 minutes on 13 devices in 9 different locations

atomic quartz
#

to step in, we know, there is a company wide incident right now over the last 30 minutes about Terminal's server driven integration being degraded and we're working on fixing it and sending comms

#

(that's separate to any other prior issue you're referring to).

inner oracle
#

This is escalated to our CEO, it's causing a major outage, we need comms in reltime, please!!!

atomic quartz
#

@inner oracle I'd suggest reaching out to https://support.stripe.com/?contact=true so we can keep you in the loop on this incident. I assure you it's the highest priority right now and it's all hands on deck!

inner oracle
#

If we switch to legacy non-server driven payment, will this resolve the issue for now?

atomic quartz
#

unclear, it's an active situation

#

the only comms I have for you right now is we're aware there's a problem and are investigating

topaz maple
#

monove-terminal-issue

inner oracle
#

any updates?

topaz maple
#

no update for now.

#

@inner oracle @rough shore are you still experiencing issues?

inner oracle
#

will check

#

seems ok for now

#

will there be a postmortem on this outage?