auth token expired mid-run while pulling Chorus call batch for competitor mention extraction

TL;DR

Pause the batch, reconnect the Chorus connection through its normal sign in flow, resume from the first call that failed rather than the start, and add a check that stops the run cleanly on an access failure instead of retrying every remaining call. Start with the Chorus batch run log at the point access failed, the connection status for Chorus, and which calls in the batch completed, 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.

auth token expired mid-run while pulling Chorus call batch for competitor mention extraction

Use this when

• You see this exact message or symptom: auth token expired mid-run while pulling Chorus call batch for competitor mention extraction
• 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 Chorus batch run log at the point access failed, the connection status for Chorus, and which calls in the batch completed, 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 time access stopped working against how many calls were already extracted, and the error each later call returned. 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: pause the batch, reconnect the Chorus connection through its normal sign in flow, resume from the first call that failed rather than the start, and add a check that stops the run cleanly on an access failure instead of retrying every remaining call. 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 resumed batch extracts competitor mentions from the remaining calls with no access errors
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

auth token expired mid-run while pulling Chorus call batch for competitor mention extraction

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: Agent workflows pulling Chorus call batches, at current versions

Why it happens

Long batch runs outlive the access granted at the start, so a batch that begins healthy fails partway and every later call errors for the same reason until the connection is renewed.

Provenance

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

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

Thread query: auth token expired mid-run while pulling Chorus call batch for competitor mention extraction

TL;DR: Pause the batch, reconnect the Chorus connection through its normal sign in flow, resume from the first call that failed rather than the start, and add a check that stops the run cleanly on an access failure instead of retrying every remaining call. Start with the Chorus batch run log at the point access failed, the connection status for Chorus, and which calls in the batch completed, 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.