parser failed on Webex VTT transcript export timestamps unparsable summary aborted

TL;DR

Normalize the VTT file before parsing by converting its timestamps to a single standard format and stripping note blocks, then rerun the summary on the cleaned file and keep the original export untouched for comparison. Start with the Webex VTT export that failed parsing, its timestamp lines, and the parser error position, 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.

parser failed on Webex VTT transcript export timestamps unparsable summary aborted

Use this when

• You see this exact message or symptom: parser failed on Webex VTT transcript export timestamps unparsable summary aborted
• 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 Webex VTT export that failed parsing, its timestamp lines, and the parser error position, 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 timestamp format on the failing lines, any note or style blocks in the file, and how Webex formatted times over one hour. 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: normalize the VTT file before parsing by converting its timestamps to a single standard format and stripping note blocks, then rerun the summary on the cleaned file and keep the original export untouched for comparison. 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 cleaned file parses to the last cue and the summary covers the end of the meeting
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

parser failed on Webex VTT transcript export timestamps unparsable summary aborted

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: Transcript parsers handling Webex VTT exports, at current versions

Why it happens

Webex VTT exports can mix timestamp shapes and include note blocks that strict parsers reject, so one unparsable line aborts the whole summary instead of skipping a cue.

Provenance

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

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

Thread query: parser failed on Webex VTT transcript export timestamps unparsable summary aborted

TL;DR: Normalize the VTT file before parsing by converting its timestamps to a single standard format and stripping note blocks, then rerun the summary on the cleaned file and keep the original export untouched for comparison. Start with the Webex VTT export that failed parsing, its timestamp lines, and the parser error position, 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.