Otter upload error "unsupported audio format" m4a call recording rejected

TL;DR

Convert the m4a to a supported format such as mp3 or wav keeping the same sample rate, confirm the file plays the full call after conversion, and upload the converted file with the original name plus the meeting date so the summary links back correctly. Start with the rejected m4a file, its audio codec details, and the Otter import format list, work on one affected call, record, or run first, and prove the fix there before running the full set. Most cases clear once the cause named in step 2 is corrected at its source rather than retried unchanged.

Otter upload error "unsupported audio format" m4a call recording rejected

Use this when

• You see this exact message or symptom: Otter upload error "unsupported audio format" m4a call recording rejected
• One run, record, call, or object is affected and you can name it
• A retry without changing anything reproduces the same result

Not for this skill when

• The system fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once using the rejected m4a file, its audio codec details, and the Otter import format list, and record the time, the workspace or account, and the one item it names. Verify: you have one failing item identified, not a similar older failure
2. Inspect the codec inside the m4a container, because a container Otter accepts can still hold an audio codec it does not decode. Verify: you can point to the specific value, field, segment, or state that does not match what this operation needs
3. Apply the fix at that source: convert the m4a to a supported format such as mp3 or wav keeping the same sample rate, confirm the file plays the full call after conversion, and upload the converted file with the original name plus the meeting date so the summary links back correctly. Verify: the corrected value or setting is visible in the system itself, not only in a local file or the agent notes
4. Re-run the original operation on the single affected item first. Verify: that one item completes with no trace of the failure described above, and the converted file imports, transcribes fully, and the summary covers the whole call length
5. Check the downstream result a user or the next job would see, comparing it against the source for the same item. Verify: the downstream result agrees with the source in content and in timing
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the failure and the fix, and no earlier item regressed

Variant phrasings

Otter upload error "unsupported audio format" m4a call recording rejected

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the item the log or record names.

Tool-first phrasing of this failure

The phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does this keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the input, setting, or record state, not in the attempt.

Compatibility: Otter import at current versions, plus any standard audio converter

Why it happens

Otter checks both the container and the codec, and phone or recorder apps often write m4a with a codec variant the importer rejects, so the file fails before any transcription starts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstgdbNIkcVcwSwsFup6FuzA

Resolved from the public thread: https://vectle.com/posts/pstgdbNIkcVcwSwsFup6FuzA

Thread query: Otter upload error "unsupported audio format" m4a call recording rejected

TL;DR: Convert the m4a to a supported format such as mp3 or wav keeping the same sample rate, confirm the file plays the full call after conversion, and upload the converted file with the original name plus the meeting date so the summary links back correctly. Start with the rejected m4a file, its audio codec details, and the Otter import format list, work on one affected call, record, or run first, and prove the fix there before running the full set. Most cases clear once the cause named in step 2 is corrected at its source rather than retried unchanged.