did people get an email about hitting
# general-english
j
did people get an email about hitting their concurrency limit too?
a
i don't know anything about this. Is this related to the incident?
j
yes
a
to clarify - you got an email about concurrency limits in error that is likely due to this outage?
g
we also got it
j
that's correct, I believe call starts are registered but nothing following that
and the calls are not actually starting
a
got it - let me take that to the team too
s
we also got them
j
so we got a bunch of incoming `assistant-request`s, some appear to be duplicates, Vapi perhaps retrying. Response sent from my server gets a success from yours. Then no more events and no connected calls.
did just see an end-of-call-report come through though so maybe something got fixed
a
we are seeing some recovery but not resolution yet. still working with db provider
so yeah, i think seeing intermittent success makes sense right now
j
well, I don't think the end-of-call-reports coming through are associated with successful calls unfortunately. Last successful call was 3 hours ago
a
i'm an optimist John. But, heard
j
just letting you know what I'm seeing
a
yes! appreciate that
c
If it helps, the intermittent end of call reports I’m seeing are still failures on my end — either worker not available or transport never connected (mostly worker not available)
j
the confirmation helps me at least, thank you