agent pagination cursor expired mid-Amplitude export: churn cohort rebuilt fr

Not specified by the original author.

TL;DR

Pagination bugs are silent because page one always works. The agent stops early when it misreads the cursor, treats a full page as the end, or deduplicates on a key that repeats across pages. Reproduce the pull with page logging, count expected versus received accounts against the analytics tool's own total, and fix the loop's end condition.

product-analytics export paginated incorrectly mid-pull: agent failed to sync half the accounts

Use this when

• The synced account count is roughly a round fraction of the real count
• No errors appear in the sync log
• The missing accounts cluster alphabetically, by date, or by another sort order

Not for this skill when

• The analytics export genuinely contains only those accounts (filter applied in the tool)
• The missing accounts were created after the export snapshot

Steps

1. Get the expected total from the analytics tool's UI or count endpoint for the same filters. Verify: the target count is known before touching the agent
2. Run the pull with per-page logging: page size, cursor value, and cumulative unique accounts. Verify: the page where progress stalls or repeats is visible
3. Inspect the loop's end condition and cursor update against the API's pagination contract. Verify: the exact pagination mistake is identified
4. Fix it, re-run, and reconcile unique accounts pulled against the expected total. Verify: pulled count matches expected, or the residual delta is explained account by account
5. Add a permanent reconciliation step: any pull short of the expected total fails the sync loudly. Verify: silent truncation cannot recur

Variant phrasings

analytics export syncs half the accounts

A related phrasing for the same underlying problem.

pagination cursor bug in agent pull

A related phrasing for the same underlying problem.

export truncated silently

A related phrasing for the same underlying problem.

Compatibility: Compatibility: paginated analytics APIs (Mixpanel, Amplitude, GA4 exports) consumed by agent sync jobs, current versions.

Why it happens

A pull that returns thousands of plausible rows gives no reason to doubt it, which is why pagination bugs survive for months. Only an independent expected total can convict them, and sort-order clustering in the missing set points straight at the loop's flaw.

Edge cases / pitfalls

• Offset pagination over changing data skips rows; cursor pagination is the fix where the API offers it.
• Dedupe keys must be the API's stable account id, never a display name that repeats.
• Reconciliation should compare unique ids, not row counts, or duplicate pages can fake completeness.

Provenance

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

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

Thread query: product-analytics export paginated incorrectly mid-pull: agent failed to sync half the accounts

TL;DR: Pagination bugs are silent because page one always works. The agent stops early when it misreads the cursor, treats a full page as the end, or deduplicates on a key that repeats across pages. Reproduce the pull with page logging, count expected versus received accounts against the analytics tool's own total, and fix the loop's end condition.

Not specified by the original author.

TL;DR

Find the last successful refresh or calculation timestamp, fix what stopped that job, force one refresh, and compare the served value against a direct query of the source. Start in the Amplitude project settings, the HTTP API ingestion log, and the Govern usage page, 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.

agent pagination cursor expired mid-Amplitude export: churn cohort rebuilt from partial event data

Use this when

• You see this exact message or symptom in Amplitude: agent pagination cursor expired mid-Amplitude export: churn cohort rebuilt from partial event data
• 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

• Amplitude 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 Amplitude project settings, the HTTP API ingestion log, and the Govern usage page 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 event payload, the required event_type and user or device id fields, the project API credential in the job config, and the cohort definition, and check the last successful refresh timestamp, the forced refresh result, and the served value versus the direct source query. 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: find the last successful refresh or calculation timestamp, fix what stopped that job, force one refresh, and compare the served value against a direct query of the source. Verify: the corrected value or setting is visible in Amplitude itself, not only in a local config file
4. Re-run the original operation on the single affected item first: replay one hour of events through the HTTP API with a corrected payload, then restart the nightly job. Verify: that one item completes with no trace of the error text from the block above
5. Put a guardrail on the agent run before widening it: cap retries and runtime for this step, require the agent to cite the record it acted on, and stop the run if the same item fails twice with the same text. Verify: a deliberately repeated failure stops the run and is reported instead of looping or being marked as success
6. Check the downstream result a user or the next job would see: the event count in Amplitude for the affected accounts and the cohort membership after the next sync. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
7. 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

agent pagination cursor expired mid-Amplitude export: churn cohort rebuilt from partial event data

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

Amplitude 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 agent pagination cursor expired mid-Amplitude export: churn cohort rebuilt from partial event data 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: Amplitude HTTP API v2 and cohort sync, Python or HTTP ingestion jobs, current Amplitude project settings. The steps assume you can read the job or build log and change the named object in Amplitude.

Why it happens

In Amplitude, this failure usually means an upstream refresh stopped or a cached or default value is being served in place of a freshly calculated one, so the surface looks plausible while being old. 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_d1WTcLSQEARS6D8RgdmW8g

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

Thread query: agent pagination cursor expired mid-Amplitude export: churn cohort rebuilt from partial event data

TL;DR: Find the last successful refresh or calculation timestamp, fix what stopped that job, force one refresh, and compare the served value against a direct query of the source. Start in the Amplitude project settings, the HTTP API ingestion log, and the Govern usage page, 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.

Not specified by the original author.

TL;DR

Find the last successful refresh or calculation timestamp, fix what stopped that job, force one refresh, and compare the served value against a direct query of the source. Start in the Amplitude project settings, the HTTP API ingestion log, and the Govern usage page, 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.

agent pagination cursor expired mid-Amplitude export: churn cohort rebuilt from partial event data

Use this when

• You see this exact message or symptom in Amplitude: agent pagination cursor expired mid-Amplitude export: churn cohort rebuilt from partial event data
• 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

• Amplitude 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 Amplitude project settings, the HTTP API ingestion log, and the Govern usage page 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 event payload, the required event_type and user or device id fields, the project API credential in the job config, and the cohort definition, and check the last successful refresh timestamp, the forced refresh result, and the served value versus the direct source query. 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: find the last successful refresh or calculation timestamp, fix what stopped that job, force one refresh, and compare the served value against a direct query of the source. Verify: the corrected value or setting is visible in Amplitude itself, not only in a local config file
4. Re-run the original operation on the single affected item first: replay one hour of events through the HTTP API with a corrected payload, then restart the nightly job. Verify: that one item completes with no trace of the error text from the block above
5. Put a guardrail on the agent run before widening it: cap retries and runtime for this step, require the agent to cite the record it acted on, and stop the run if the same item fails twice with the same text. Verify: a deliberately repeated failure stops the run and is reported instead of looping or being marked as success
6. Check the downstream result a user or the next job would see: the event count in Amplitude for the affected accounts and the cohort membership after the next sync. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
7. 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

agent pagination cursor expired mid-Amplitude export: churn cohort rebuilt from partial event data

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

Amplitude 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 agent pagination cursor expired mid-Amplitude export: churn cohort rebuilt from partial event data 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: Amplitude HTTP API v2 and cohort sync, Python or HTTP ingestion jobs, current Amplitude project settings. The steps assume you can read the job or build log and change the named object in Amplitude.

Why it happens

In Amplitude, this failure usually means an upstream refresh stopped or a cached or default value is being served in place of a freshly calculated one, so the surface looks plausible while being old. 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_55m8dOXOCQgYvICP8GLOTg

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

Thread query: agent pagination cursor expired mid-Amplitude export: churn cohort rebuilt from partial event data

TL;DR: Find the last successful refresh or calculation timestamp, fix what stopped that job, force one refresh, and compare the served value against a direct query of the source. Start in the Amplitude project settings, the HTTP API ingestion log, and the Govern usage page, 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.