## TL;DR
Move the wait to the job status endpoint with a deadline and a status log line per poll, shorten the work per call, and surface the underlying job id so its own log can be read. Start in the Mixpanel project settings, the import API response log, and the Lexicon, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

```text
Mixpanel JQL query timeout script exceeded execution limit when scoring weekly active accounts for churn risk
```

## Use this when
- You see this exact message or symptom in Mixpanel: Mixpanel JQL query timeout script exceeded execution limit when scoring weekly active accounts for churn risk
- One run, record, build, or object is affected and you can name it
- A retry without changing anything reproduces the same text

## Not for this skill when
- Mixpanel 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 in the Mixpanel project settings, the import API response log, and the Lexicon and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the import payload, the project credential used by the job, the distinct_id values, and the JQL or cohort definition, and check the job id, the polling deadline, the status log, and the split of the work into smaller ranges. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: move the wait to the job status endpoint with a deadline and a status log line per poll, shorten the work per call, and surface the underlying job id so its own log can be read. Verify: the corrected value or setting is visible in Mixpanel itself, not only in a local config file
4. Re-run the original operation on the single affected item first: re-import a one day slice through the import API, then re-run the scoring query on that slice only. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the event volume for at-risk accounts in Explore and the updated risk list after scoring. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
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 error and the changed setting, and no earlier item regressed

## Variant phrasings
### Mixpanel JQL query timeout script exceeded execution limit when scoring weekly active accounts for churn risk
The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.
### Mixpanel version of this failure
The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.
### Why does mixpanel JQL query timeout script exceeded execution limit when scoring weekly active accounts for churn risk 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 object state, not in the attempt.

Compatibility: Mixpanel import API and JQL, service account authentication, current Mixpanel project settings. The steps assume you can read the job or build log and change the named object in Mixpanel.

## Why it happens
In Mixpanel, this failure usually means a synchronous wait or an unbounded poll hid an asynchronous job that was still running, failed elsewhere, or finished without the waiter noticing. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

## Provenance

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