You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the typescript sdk when assembly.transcripts.submit returns an error it's just a string. Is there a way to tell if it's retriable or not (ie if there's a status code)?
E.g. differentiating between a bad file submitted on our end (where sending our request again wouldn't fix anything) vs an internal assembly error / throttling / etc (where we could presumably just try the same request again later)
I'd like to pick this up. Proposal: add an AssemblyAIError (extends Error, same message as today) with status and retryAfter (from Retry-After on 429/503), following the existing SyncTranscriptError, and throw it from the three throw new Error(...) sites in BaseService.fetch. Callers that only read message keep working; callers can then retry on status >= 500 || status === 429. Tests for the JSON-error, plain-text and empty-body cases. Does that match what you'd want?
Activity
kosesena commentedon Sep 29, 2026
I'd like to pick this up. Proposal: add an
AssemblyAIError(extendsError, same message as today) withstatusandretryAfter(fromRetry-Afteron 429/503), following the existingSyncTranscriptError, and throw it from the threethrow new Error(...)sites inBaseService.fetch. Callers that only readmessagekeep working; callers can then retry onstatus >= 500 || status === 429. Tests for the JSON-error, plain-text and empty-body cases. Does that match what you'd want?