Closed lippytak closed 9 years ago
Eeep, my first try took ~40 mins. I'll bet this has to do with the volume of the start of the month. @daguar let's break and discuss this now.
@daguar is looking into Twilio logs. I am going to:
CA line is working as usual.
Dev appears to be working with normal latency (one attempt from me).
Twilio status board says things are all good: http://status.twilio.com/
It doesn't appear that queuing is the issue (Twilio logs say no queue time on responses).
Still seeing intermittent problems, even on a separate subaccount. I texted 8 EBT numbers in quick succession and only got 6 responses:
Hmmm....
Seems intermittent now and equally affecting all phone numbers, so we're thinking this is a Twilio side issue. Still looking it but consider this officially downgraded from EBF-status.
We now have confirmation that there is a Twilio-level issue happening — will report more as we find out.
@daguar I just updated the metrics data as of 2:25pm and glanced through the ~300 balance checks from today. As always there are a few imperfect experience (see below) but I didn't see a single instance of someone complaining about the delay. So I think we're :+1: and no need to alert users. Feel free to look through yourself and LMK if anything jumps out at you.
BTW the above example is another good case for https://github.com/codeforamerica/balance/issues/272
Also I'm going to message that user personally from our textit.in account right now.
Via our one-of-a-kind Twilio dev evangelist:
Hey all, Torkel is deploying a fix as we speak. Your transcriptions should be working properly in the very near future. Really appreciate you tracking this one down for us. I think y'all are are hooked up on credits through Twilio.org, but if you need more dropped in your account in the future, or if y'all need some Twilio t-shirts, let me know.
Just tested with 10 simultaneous balance checks and got back LIGHTNING FAST (~60 seconds) responses:
Looks like this issue is :+1:
(oops wrong screenshot...edited!)
From our loving user Francesca:
@daguar let's look into this today, though I wouldn't say this requires an immediate fix unless it's happening in all cases. I'll do some manual testing now and report back here.