Skip to content
This repository was archived by the owner on Mar 23, 2026. It is now read-only.
This repository was archived by the owner on Mar 23, 2026. It is now read-only.

bug: TranscribeService should fail for audio sizes exceeding 4 hours. #12423

@scapeshift-ojones

Description

@scapeshift-ojones

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

when attempting to submit a job based on an audio file in an s3 bucket which exceeds 4 hours, Localstack Transcribe happily accepts and starts working

Expected Behavior

Real Transcribe service behavior when attempting to submit a job based on an audio file in an s3 bucket which exceeds 4 hours:
Failure reason Invalid file size: file size too large. Maximum audio duration is 4.000000 hours.Check the length of the file and try your request again.

How are you starting LocalStack?

With a docker-compose file

Steps To Reproduce

submit a job using an audio file that exceeds 4 hours.

For example:

https://media.blubrry.com/takeituneasy/content.blubrry.com/takeituneasy/lex_ai_deepseek_dylan_patel_nathan_lambert.mp3

Environment

- OS: MacOS 13.7.1 Ventura
- arm64 / M1

localstack status:
│ Runtime version │ 4.2.1.dev51                                           │
│ Docker image    │ tag: latest, id: bd4219d016fd, 📆 2025-03-14T00:44:02 │
│ Runtime status  │ ✔ running (name: "localstack-main", IP: 172.17.0.2) 

LocalStack CLI 4.1.1

Anything else?

could be related to, or worked on at the same time as, issues/10988

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions