tl;dv summary error highlight timestamps drift two minutes from video

TL;DR

Re-sync the highlight by regenerating timestamps from the transcript of the processed video rather than the uploaded file timing, then shift the affected highlights by the measured two minute offset and spot check three of them against the player. Start with a tl;dv highlight and the same moment in the video player, the transcript timestamps around it, and the recording frame rate source, 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.

tl;dv summary error highlight timestamps drift two minutes from video

Use this when

• You see this exact message or symptom: tl;dv summary error highlight timestamps drift two minutes from video
• 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 a tl;dv highlight and the same moment in the video player, the transcript timestamps around it, and the recording frame rate source, 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 offset between a spoken phrase in the video and its transcript timestamp at the start, middle, and end of the call. 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: re-sync the highlight by regenerating timestamps from the transcript of the processed video rather than the uploaded file timing, then shift the affected highlights by the measured two minute offset and spot check three of them against the player. 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 three sampled highlights start within a second of the spoken phrase in the player
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

tl;dv summary error highlight timestamps drift two minutes from video

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: tl;dv at current versions, for recordings imported or trimmed after upload

Why it happens

If the platform trims silence or a waiting room segment from the video but not from the timing source, every later timestamp drifts by that trimmed length and highlights point at the wrong moment.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_d-0zg6g14lFAjsytNraFYg

Resolved from the public thread: https://vectle.com/posts/pst_d-0zg6g14lFAjsytNraFYg

Thread query: tl;dv summary error highlight timestamps drift two minutes from video

TL;DR: Re-sync the highlight by regenerating timestamps from the transcript of the processed video rather than the uploaded file timing, then shift the affected highlights by the measured two minute offset and spot check three of them against the player. Start with a tl;dv highlight and the same moment in the video player, the transcript timestamps around it, and the recording frame rate source, 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.