Skip to content
This repository has been archived by the owner on Jan 23, 2024. It is now read-only.

Failed transcription with 8-minute lag on callback from API #304

Open
daguar opened this issue May 6, 2015 · 2 comments
Open

Failed transcription with 8-minute lag on callback from API #304

daguar opened this issue May 6, 2015 · 2 comments
Assignees
@daguar
Labels
bug

Comments

@daguar
Copy link
Contributor

daguar commented May 6, 2015

Found via our awesome new monitoring! I've submitted a ticket to Twilio.
@daguar daguar added the bug label May 6, 2015
@daguar daguar self-assigned this May 6, 2015
@daguar
Copy link
Contributor Author

daguar commented May 6, 2015

So, super fascinating — the transcription appears to have eventually succeeded around 8am this morning, triggering an 8-hour-delayed response back to the user.

@alanjosephwilliams
Copy link

Looking forward to hearing Twilio's response

On Wed, May 6, 2015 at 11:11 AM, Dave Guarino [email protected]
wrote:

So, super fascinating — the transcription appears to have eventually
succeeded around 8am this morning, triggering an 8-hour-delayed response
back to the user.

—
Reply to this email directly or view it on GitHub
#304 (comment)
.

t: @alanjosephwilli
p: 817 713 6264

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@daguar daguar

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@daguar @alanjosephwilliams