[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-posthog-diagnosing-failed-warehouse-syncs":3,"mdc--qe6swf-key":44,"related-repo-posthog-diagnosing-failed-warehouse-syncs":2003,"related-org-posthog-diagnosing-failed-warehouse-syncs":2125},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":29,"repoUrl":30,"updatedAt":31,"license":32,"forks":33,"topics":34,"repo":39,"sourceUrl":42,"mdContent":43},"diagnosing-failed-warehouse-syncs","diagnose failed data warehouse syncs","Diagnose why a data warehouse sync is failing and recommend the right recovery action. Use when the user asks \"why isn't my Stripe\u002FPostgres\u002FHubspot sync working?\", \"this table has been stuck for hours\", \"the data in the warehouse looks wrong\", or wants to troubleshoot a specific source or schema. Covers source-level vs schema-level failures, stuck Running states, credential and schema-drift errors, incremental-field misconfig, CDC prerequisite failures, and the cancel \u002F reload \u002F resync \u002F delete-data recovery actions.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"posthog","PostHog","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fposthog.png",[12,14,17,20,23,26],{"name":9,"slug":8,"type":13},"tag",{"name":15,"slug":16,"type":13},"Data Engineering","data-engineering",{"name":18,"slug":19,"type":13},"Monitoring","monitoring",{"name":21,"slug":22,"type":13},"Data Warehouse","data-warehouse",{"name":24,"slug":25,"type":13},"ETL","etl",{"name":27,"slug":28,"type":13},"Debugging","debugging",59,"https:\u002F\u002Fgithub.com\u002FPostHog\u002Fai-plugin","2026-06-18T08:19:16.316755",null,11,[35,36,37,38],"claude-code-plugin","codex-plugin","cursor-plugin","gemini-cli-extension",{"repoUrl":30,"stars":29,"forks":33,"topics":40,"description":41},[35,36,37,38],"Official PostHog plugin for Claude Code, Cursor, Gemini, Codex and other AI coding tools","https:\u002F\u002Fgithub.com\u002FPostHog\u002Fai-plugin\u002Ftree\u002FHEAD\u002Fskills\u002Fdiagnosing-failed-warehouse-syncs","---\nname: diagnosing-failed-warehouse-syncs\ndescription: >\n  Diagnose why a data warehouse sync is failing and recommend the right recovery action. Use when the user asks \"why\n  isn't my Stripe\u002FPostgres\u002FHubspot sync working?\", \"this table has been stuck for hours\", \"the data in the warehouse\n  looks wrong\", or wants to troubleshoot a specific source or schema. Covers source-level vs schema-level failures,\n  stuck Running states, credential and schema-drift errors, incremental-field misconfig, CDC prerequisite failures,\n  and the cancel \u002F reload \u002F resync \u002F delete-data recovery actions.\n---\n\n# Diagnosing failed data warehouse syncs\n\nWork top-down when a data warehouse source or table is failing, stuck, or producing bad data: source → schema →\nrecovery action. Do **not** jump straight to \"resync from scratch\" — that discards synced data and restarts from\nzero, which is rarely the right first step.\n\n## When to use this skill\n\n- The user reports a specific sync is failing (e.g. \"my Stripe source is red\")\n- A table has been in `Running` state far longer than expected\n- Data in a warehouse table is stale, missing rows, or looks corrupt\n- Latest rows aren't appearing despite the schema being marked `Completed`\n- The user is choosing between cancel \u002F reload \u002F resync \u002F delete-data and isn't sure which\n- Another skill — typically `auditing-warehouse-source-health` — has surfaced a failing source or schema and the user\n  wants to dig into it\n\nBoth entry points (user-reported and audit-handoff) use the same workflow; the audit just means you already know\nwhich item to diagnose and can skip Step 1's discovery search.\n\n## Available tools\n\n| Tool                                                   | Purpose                                                                    |\n| ------------------------------------------------------ | -------------------------------------------------------------------------- |\n| `external-data-sources-list`                           | List all sources with connection status and latest error                   |\n| `external-data-sources-retrieve`                       | Full details for one source including all its schemas                      |\n| `external-data-schemas-list`                           | All table schemas across all sources, with per-table status + latest_error |\n| `external-data-schemas-retrieve`                       | Full details for one schema including sync_type_config                     |\n| `external-data-schemas-cancel`                         | Cancel a sync currently in `Running` state                                 |\n| `external-data-schemas-reload`                         | Trigger a sync using the configured sync method (respects incremental)     |\n| `external-data-schemas-resync`                         | Full resync — wipes synced data and restarts. Destructive                  |\n| `external-data-schemas-delete-data`                    | Delete the synced table but keep the schema entry                          |\n| `external-data-schemas-partial-update`                 | Change sync_type \u002F incremental_field \u002F cdc_table_mode                      |\n| `external-data-sources-partial-update`                 | Update a source's credentials (`job_inputs`) after rotation                |\n| `external-data-sources-reload`                         | Retrigger syncs for every enabled schema on a source                       |\n| `external-data-sources-refresh-schemas`                | Re-fetch the source's table list to pick up new tables                     |\n| `external-data-sources-check-cdc-prerequisites-create` | Verify Postgres CDC setup for a source                                     |\n| `external-data-schemas-incremental-fields-create`      | Refresh candidate incremental fields when the source schema has changed    |\n| `external-data-sources-webhook-info-retrieve`          | Check webhook registration state and external service status               |\n| `external-data-sources-create-webhook-create`          | Re-register a webhook that was lost or never registered                    |\n| `external-data-sources-update-webhook-inputs-create`   | Update the signing secret after rotation on the source side                |\n| `external-data-sources-delete-webhook-create`          | Remove a broken webhook before re-registering                              |\n\n## Workflow\n\n### Step 1 — Locate the failing item\n\nIf the user named a source, go straight to `external-data-sources-retrieve`. Otherwise start with\n`external-data-sources-list` and `external-data-schemas-list` to find what's red.\n\nTwo kinds of failure:\n\n- **Source-level** (`ExternalDataSource.status = \"Error\"`): the connection itself is broken — credentials expired,\n  host unreachable, account disabled. Affects every table.\n- **Schema-level** — the source connects fine but one or more tables are failing. In the serialized API response\n  from `external-data-schemas-list`, look for `status` values `\"Failed\"`, `\"Billing limits\"`, or `\"Billing limits\ntoo low\"`. (The underlying model enum values are `BillingLimitReached` and `BillingLimitTooLow`, but the\n  serializer rewrites them — match on both the human-readable and enum forms to be safe.)\n\nA source can look `Completed` at the top level while one of its schemas is `Failed` — always check both.\n\n### Step 2 — Classify the schema status\n\nFrom `external-data-schemas-list`, each schema has a `status`:\n\n| Status                                                              | Meaning                                    | Usually means                          |\n| ------------------------------------------------------------------- | ------------------------------------------ | -------------------------------------- |\n| `Running`                                                           | Sync currently executing                   | Normal, unless stuck for hours         |\n| `Completed`                                                         | Last sync finished successfully            | Healthy                                |\n| `Failed`                                                            | Last sync errored — see `latest_error`     | Needs diagnosis                        |\n| `Paused`                                                            | User disabled sync (`should_sync = false`) | Intentional                            |\n| `Billing limits` (serializer) \u002F `BillingLimitReached` (enum)        | Team hit its warehouse row quota           | Billing issue, not a technical failure |\n| `Billing limits too low` (serializer) \u002F `BillingLimitTooLow` (enum) | Team has insufficient credit               | Billing issue                          |\n\nAlways check `last_synced_at` alongside status. A schema in `Running` with `last_synced_at` from 12 hours ago is\nalmost certainly stuck, even though the status isn't `Failed`.\n\n### Step 3 — Interpret `latest_error`\n\nMap the `latest_error` string to a root cause. Common patterns:\n\n| Error substring                                              | Root cause                                                 | Fix                                                                                   |\n| ------------------------------------------------------------ | ---------------------------------------------------------- | ------------------------------------------------------------------------------------- |\n| `authentication failed`, `401`, `403`, `invalid credentials` | Credentials expired or rotated                             | User rotates creds, then `external-data-sources-partial-update` with new `job_inputs` |\n| `Could not establish session to SSH gateway`                 | SSH tunnel misconfigured or remote host down               | User checks SSH host\u002Fkey\u002Fbastion                                                      |\n| `Primary key required for incremental syncs`                 | Table has no PK and sync_type is `incremental`\u002F`cdc`       | Either add PK in source, or switch schema to `full_refresh`                           |\n| `primary keys for this table are not unique`                 | Declared PK columns aren't actually unique                 | Pick different PK columns via `partial-update`                                        |\n| `Integration matching query does not exist`                  | Source's saved integration was deleted                     | Recreate the source                                                                   |\n| `column \"X\" does not exist`, `does not have a column named`  | Schema drift — incremental field or tracked column removed | Use `incremental-fields-create` to re-detect, then `partial-update`                   |\n| `relation \"...\" does not exist`                              | Source table was dropped\u002Frenamed                           | Remove schema or rename source-side                                                   |\n| `SSL`, `connection refused`, `timeout`, `unreachable`        | Network \u002F firewall \u002F host reachability                     | User side — check host\u002Fport\u002Fallowlist                                                 |\n| `replication slot`, `publication`, `wal_level`               | CDC prerequisites broken                                   | Run `check-cdc-prerequisites-create`; may need slot recreate                          |\n| `Schema exceeds row limit`, `billing`                        | Billing limit                                              | Upgrade plan or disable the schema                                                    |\n\nIf `latest_error` is null but the schema is `Failed`, retrieve the schema directly — the error may only be populated\non the detail view.\n\n### Step 4 — Pick the recovery action\n\nThe recovery action depends on root cause, not just status. Match the user's situation to one of these:\n\n**A. Transient failure (network blip, temporary API outage)**\n\n- Data synced so far is still valid.\n- Action: `external-data-schemas-reload` to retry using the configured sync method.\n- Incremental\u002Fappend syncs pick up where they left off.\n\n**B. Credentials expired or rotated**\n\n- Every schema under the source is failing with an auth error.\n- Action: user rotates creds → `external-data-sources-partial-update` with the new `job_inputs` → the reload happens\n  automatically when the source status flips back to running, or trigger manually with `external-data-sources-reload`.\n\n**C. Schema drift — column renamed, dropped, or type changed**\n\n- Error mentions a specific column that no longer matches the source.\n- Action: `external-data-schemas-incremental-fields-create` to get the current fields, then\n  `external-data-schemas-partial-update` with the corrected `incremental_field` \u002F `incremental_field_type` \u002F\n  `primary_key_columns`. Usually no need to wipe data.\n\n**C2. Added \u002F renamed tables in the source database**\n\n- User mentions \"I added a new table to Postgres but it isn't appearing\", or a source table was renamed.\n- Action: `external-data-sources-refresh-schemas` to pick up the new table list, then configure sync on any new\n  schemas.\n\n**D. Incremental state is wrong (duplicates, missing rows, data looks corrupt)**\n\n- Schema status may be `Completed` — this isn't a \"failure\" per se, it's bad data.\n- Action: `external-data-schemas-resync` to wipe synced data and re-import from source. Destructive but often the\n  right call for data-quality issues.\n\n**E. CDC pipeline broken on Postgres**\n\n- Error mentions replication slot, publication, WAL.\n- Action: `external-data-sources-check-cdc-prerequisites-create` to enumerate what's broken, fix on the Postgres\n  side, then `external-data-schemas-reload`. If the WAL position was lost, a `resync` is sometimes unavoidable.\n\n**F. Sync is stuck in `Running` for hours**\n\n- Check `last_synced_at`. If it's hours old and still `Running`, the job is orphaned.\n- Action: `external-data-schemas-cancel` to stop it, then `external-data-schemas-reload`.\n\n**G. Table data is corrupt but you want to keep the schema config**\n\n- Action: `external-data-schemas-delete-data` to drop the synced table but preserve the schema entry. Next reload\n  re-imports from scratch without losing the configured sync_type\u002Fincremental_field.\n\n**H. Billing limit**\n\n- Action isn't technical. Explain the limit, recommend upgrading the plan or disabling lower-priority schemas so the\n  important ones fit under quota.\n\n**I. Webhook-backed schema isn't receiving events**\n\n- Symptoms: schema has `sync_type: \"webhook\"`, initial bulk sync finished, but no new rows arrive despite activity on\n  the source side. Status may still read `Completed` because the bulk sync (the safety-net cadence) is succeeding —\n  the problem is the push path.\n- Action:\n  1. `external-data-sources-webhook-info-retrieve({source_id})`.\n  2. If `exists: false` → the webhook was never registered, or was deleted. Call `create-webhook-create` to\n     register it.\n  3. If `exists: true` but `external_status.error` is set → typically \"API key doesn't have permission to read\n     webhooks\" or similar. The webhook may have been deleted on the source's dashboard. Re-create it.\n  4. If `external_status.status` isn't `\"enabled\"` → the source disabled the webhook (usually after repeated\n     delivery failures). Re-enable or re-register.\n  5. If payloads are arriving but failing signature verification → the signing secret was rotated. Get the new\n     one from the source's dashboard and call `update-webhook-inputs-create({source_id}, {inputs:\n{signing_secret: \"...\"}})`.\n- After any fix, check the source's webhook logs (on their side) to confirm PostHog is now responding 2xx.\n\n### Step 5 — Confirm before destructive actions\n\nThree recovery actions discard data and cannot be undone:\n\n- `external-data-schemas-resync` — wipes synced rows, re-imports from scratch\n- `external-data-schemas-delete-data` — drops the synced table\n- `external-data-sources-destroy` — deletes the source and all its schemas\n\nAlways present the fix you're proposing and wait for explicit approval before calling any of these. \"Just try\nresync\" is rarely the right default.\n\n## Example interaction\n\n```text\nUser: \"Our Stripe sync is broken, can you check?\"\n\nAgent:\n- external-data-sources-list → find Stripe source, status = Error\n- external-data-sources-retrieve({id}) → latest_error: \"authentication failed: 401 Unauthorized\"\n- Report: \"Your Stripe source's API key is no longer authenticating.\n   All 8 tables under it are failing with 401s. This usually means the key was rotated on the Stripe side.\n\n   To fix:\n   1. Grab a fresh restricted API key from the Stripe dashboard.\n   2. I'll update the source with the new key.\n   3. Syncs will resume automatically — no data loss.\n\n   Paste the new key here when ready.\"\n\nUser: \"sk_live_...\"\n\nAgent:\n- external-data-sources-partial-update({id}, {job_inputs: {stripe_secret_key: \"sk_live_...\"}})\n- external-data-sources-reload({id}) to trigger retry\n- Report: \"Updated and re-triggered. Check back in a few minutes — latest_error should clear.\"\n```\n\n## Important notes\n\n- **Source status overrides schema status for diagnosis.** If the source is `Error`, nothing under it will work;\n  fixing the source usually fixes all its schemas at once.\n- **`Running` isn't always healthy.** Cross-check `last_synced_at`. A sync stuck in `Running` needs `cancel` then\n  `reload`, not `resync`.\n- **Resync is destructive.** It discards synced data. Only recommend it when the data itself is bad (duplicates,\n  missing rows, corrupt) or when recovery genuinely requires a clean slate (lost WAL position on CDC). Never use it\n  as a first-try for transient errors.\n- **Delete-data preserves config.** When a user says \"I just want to start this table over from scratch\", prefer\n  `delete-data` + `reload` over `resync` + new schema entry — it keeps the configured sync_type \u002F incremental_field\n  \u002F PK setup.\n- **Billing limits aren't technical failures.** Don't try to retry or reconfigure your way out. Route to billing.\n- **Webhook failures can hide behind a green status.** A webhook-type schema whose bulk fallback sync succeeded looks\n  `Completed` even when the push channel is broken. When users say \"my data is hours behind\" on a webhook schema,\n  call `webhook-info-retrieve` before looking at schema status. Webhook issues don't surface on\n  `external-data-schemas-list`.\n",{"data":45,"body":46},{"name":4,"description":6},{"type":47,"children":48},"root",[49,58,72,79,137,142,148,497,503,510,536,541,626,646,652,671,857,891,902,914,1290,1309,1315,1320,1328,1353,1361,1394,1402,1452,1460,1479,1487,1513,1521,1555,1570,1609,1617,1631,1639,1647,1655,1774,1780,1785,1819,1824,1830,1842,1848],{"type":50,"tag":51,"props":52,"children":54},"element","h1",{"id":53},"diagnosing-failed-data-warehouse-syncs",[55],{"type":56,"value":57},"text","Diagnosing failed data warehouse syncs",{"type":50,"tag":59,"props":60,"children":61},"p",{},[62,64,70],{"type":56,"value":63},"Work top-down when a data warehouse source or table is failing, stuck, or producing bad data: source → schema →\nrecovery action. Do ",{"type":50,"tag":65,"props":66,"children":67},"strong",{},[68],{"type":56,"value":69},"not",{"type":56,"value":71}," jump straight to \"resync from scratch\" — that discards synced data and restarts from\nzero, which is rarely the right first step.",{"type":50,"tag":73,"props":74,"children":76},"h2",{"id":75},"when-to-use-this-skill",[77],{"type":56,"value":78},"When to use this skill",{"type":50,"tag":80,"props":81,"children":82},"ul",{},[83,89,103,108,119,124],{"type":50,"tag":84,"props":85,"children":86},"li",{},[87],{"type":56,"value":88},"The user reports a specific sync is failing (e.g. \"my Stripe source is red\")",{"type":50,"tag":84,"props":90,"children":91},{},[92,94,101],{"type":56,"value":93},"A table has been in ",{"type":50,"tag":95,"props":96,"children":98},"code",{"className":97},[],[99],{"type":56,"value":100},"Running",{"type":56,"value":102}," state far longer than expected",{"type":50,"tag":84,"props":104,"children":105},{},[106],{"type":56,"value":107},"Data in a warehouse table is stale, missing rows, or looks corrupt",{"type":50,"tag":84,"props":109,"children":110},{},[111,113],{"type":56,"value":112},"Latest rows aren't appearing despite the schema being marked ",{"type":50,"tag":95,"props":114,"children":116},{"className":115},[],[117],{"type":56,"value":118},"Completed",{"type":50,"tag":84,"props":120,"children":121},{},[122],{"type":56,"value":123},"The user is choosing between cancel \u002F reload \u002F resync \u002F delete-data and isn't sure which",{"type":50,"tag":84,"props":125,"children":126},{},[127,129,135],{"type":56,"value":128},"Another skill — typically ",{"type":50,"tag":95,"props":130,"children":132},{"className":131},[],[133],{"type":56,"value":134},"auditing-warehouse-source-health",{"type":56,"value":136}," — has surfaced a failing source or schema and the user\nwants to dig into it",{"type":50,"tag":59,"props":138,"children":139},{},[140],{"type":56,"value":141},"Both entry points (user-reported and audit-handoff) use the same workflow; the audit just means you already know\nwhich item to diagnose and can skip Step 1's discovery search.",{"type":50,"tag":73,"props":143,"children":145},{"id":144},"available-tools",[146],{"type":56,"value":147},"Available tools",{"type":50,"tag":149,"props":150,"children":151},"table",{},[152,171],{"type":50,"tag":153,"props":154,"children":155},"thead",{},[156],{"type":50,"tag":157,"props":158,"children":159},"tr",{},[160,166],{"type":50,"tag":161,"props":162,"children":163},"th",{},[164],{"type":56,"value":165},"Tool",{"type":50,"tag":161,"props":167,"children":168},{},[169],{"type":56,"value":170},"Purpose",{"type":50,"tag":172,"props":173,"children":174},"tbody",{},[175,193,210,227,244,268,285,302,319,336,361,378,395,412,429,446,463,480],{"type":50,"tag":157,"props":176,"children":177},{},[178,188],{"type":50,"tag":179,"props":180,"children":181},"td",{},[182],{"type":50,"tag":95,"props":183,"children":185},{"className":184},[],[186],{"type":56,"value":187},"external-data-sources-list",{"type":50,"tag":179,"props":189,"children":190},{},[191],{"type":56,"value":192},"List all sources with connection status and latest error",{"type":50,"tag":157,"props":194,"children":195},{},[196,205],{"type":50,"tag":179,"props":197,"children":198},{},[199],{"type":50,"tag":95,"props":200,"children":202},{"className":201},[],[203],{"type":56,"value":204},"external-data-sources-retrieve",{"type":50,"tag":179,"props":206,"children":207},{},[208],{"type":56,"value":209},"Full details for one source including all its schemas",{"type":50,"tag":157,"props":211,"children":212},{},[213,222],{"type":50,"tag":179,"props":214,"children":215},{},[216],{"type":50,"tag":95,"props":217,"children":219},{"className":218},[],[220],{"type":56,"value":221},"external-data-schemas-list",{"type":50,"tag":179,"props":223,"children":224},{},[225],{"type":56,"value":226},"All table schemas across all sources, with per-table status + latest_error",{"type":50,"tag":157,"props":228,"children":229},{},[230,239],{"type":50,"tag":179,"props":231,"children":232},{},[233],{"type":50,"tag":95,"props":234,"children":236},{"className":235},[],[237],{"type":56,"value":238},"external-data-schemas-retrieve",{"type":50,"tag":179,"props":240,"children":241},{},[242],{"type":56,"value":243},"Full details for one schema including sync_type_config",{"type":50,"tag":157,"props":245,"children":246},{},[247,256],{"type":50,"tag":179,"props":248,"children":249},{},[250],{"type":50,"tag":95,"props":251,"children":253},{"className":252},[],[254],{"type":56,"value":255},"external-data-schemas-cancel",{"type":50,"tag":179,"props":257,"children":258},{},[259,261,266],{"type":56,"value":260},"Cancel a sync currently in ",{"type":50,"tag":95,"props":262,"children":264},{"className":263},[],[265],{"type":56,"value":100},{"type":56,"value":267}," state",{"type":50,"tag":157,"props":269,"children":270},{},[271,280],{"type":50,"tag":179,"props":272,"children":273},{},[274],{"type":50,"tag":95,"props":275,"children":277},{"className":276},[],[278],{"type":56,"value":279},"external-data-schemas-reload",{"type":50,"tag":179,"props":281,"children":282},{},[283],{"type":56,"value":284},"Trigger a sync using the configured sync method (respects incremental)",{"type":50,"tag":157,"props":286,"children":287},{},[288,297],{"type":50,"tag":179,"props":289,"children":290},{},[291],{"type":50,"tag":95,"props":292,"children":294},{"className":293},[],[295],{"type":56,"value":296},"external-data-schemas-resync",{"type":50,"tag":179,"props":298,"children":299},{},[300],{"type":56,"value":301},"Full resync — wipes synced data and restarts. Destructive",{"type":50,"tag":157,"props":303,"children":304},{},[305,314],{"type":50,"tag":179,"props":306,"children":307},{},[308],{"type":50,"tag":95,"props":309,"children":311},{"className":310},[],[312],{"type":56,"value":313},"external-data-schemas-delete-data",{"type":50,"tag":179,"props":315,"children":316},{},[317],{"type":56,"value":318},"Delete the synced table but keep the schema entry",{"type":50,"tag":157,"props":320,"children":321},{},[322,331],{"type":50,"tag":179,"props":323,"children":324},{},[325],{"type":50,"tag":95,"props":326,"children":328},{"className":327},[],[329],{"type":56,"value":330},"external-data-schemas-partial-update",{"type":50,"tag":179,"props":332,"children":333},{},[334],{"type":56,"value":335},"Change sync_type \u002F incremental_field \u002F cdc_table_mode",{"type":50,"tag":157,"props":337,"children":338},{},[339,348],{"type":50,"tag":179,"props":340,"children":341},{},[342],{"type":50,"tag":95,"props":343,"children":345},{"className":344},[],[346],{"type":56,"value":347},"external-data-sources-partial-update",{"type":50,"tag":179,"props":349,"children":350},{},[351,353,359],{"type":56,"value":352},"Update a source's credentials (",{"type":50,"tag":95,"props":354,"children":356},{"className":355},[],[357],{"type":56,"value":358},"job_inputs",{"type":56,"value":360},") after rotation",{"type":50,"tag":157,"props":362,"children":363},{},[364,373],{"type":50,"tag":179,"props":365,"children":366},{},[367],{"type":50,"tag":95,"props":368,"children":370},{"className":369},[],[371],{"type":56,"value":372},"external-data-sources-reload",{"type":50,"tag":179,"props":374,"children":375},{},[376],{"type":56,"value":377},"Retrigger syncs for every enabled schema on a source",{"type":50,"tag":157,"props":379,"children":380},{},[381,390],{"type":50,"tag":179,"props":382,"children":383},{},[384],{"type":50,"tag":95,"props":385,"children":387},{"className":386},[],[388],{"type":56,"value":389},"external-data-sources-refresh-schemas",{"type":50,"tag":179,"props":391,"children":392},{},[393],{"type":56,"value":394},"Re-fetch the source's table list to pick up new tables",{"type":50,"tag":157,"props":396,"children":397},{},[398,407],{"type":50,"tag":179,"props":399,"children":400},{},[401],{"type":50,"tag":95,"props":402,"children":404},{"className":403},[],[405],{"type":56,"value":406},"external-data-sources-check-cdc-prerequisites-create",{"type":50,"tag":179,"props":408,"children":409},{},[410],{"type":56,"value":411},"Verify Postgres CDC setup for a source",{"type":50,"tag":157,"props":413,"children":414},{},[415,424],{"type":50,"tag":179,"props":416,"children":417},{},[418],{"type":50,"tag":95,"props":419,"children":421},{"className":420},[],[422],{"type":56,"value":423},"external-data-schemas-incremental-fields-create",{"type":50,"tag":179,"props":425,"children":426},{},[427],{"type":56,"value":428},"Refresh candidate incremental fields when the source schema has changed",{"type":50,"tag":157,"props":430,"children":431},{},[432,441],{"type":50,"tag":179,"props":433,"children":434},{},[435],{"type":50,"tag":95,"props":436,"children":438},{"className":437},[],[439],{"type":56,"value":440},"external-data-sources-webhook-info-retrieve",{"type":50,"tag":179,"props":442,"children":443},{},[444],{"type":56,"value":445},"Check webhook registration state and external service status",{"type":50,"tag":157,"props":447,"children":448},{},[449,458],{"type":50,"tag":179,"props":450,"children":451},{},[452],{"type":50,"tag":95,"props":453,"children":455},{"className":454},[],[456],{"type":56,"value":457},"external-data-sources-create-webhook-create",{"type":50,"tag":179,"props":459,"children":460},{},[461],{"type":56,"value":462},"Re-register a webhook that was lost or never registered",{"type":50,"tag":157,"props":464,"children":465},{},[466,475],{"type":50,"tag":179,"props":467,"children":468},{},[469],{"type":50,"tag":95,"props":470,"children":472},{"className":471},[],[473],{"type":56,"value":474},"external-data-sources-update-webhook-inputs-create",{"type":50,"tag":179,"props":476,"children":477},{},[478],{"type":56,"value":479},"Update the signing secret after rotation on the source side",{"type":50,"tag":157,"props":481,"children":482},{},[483,492],{"type":50,"tag":179,"props":484,"children":485},{},[486],{"type":50,"tag":95,"props":487,"children":489},{"className":488},[],[490],{"type":56,"value":491},"external-data-sources-delete-webhook-create",{"type":50,"tag":179,"props":493,"children":494},{},[495],{"type":56,"value":496},"Remove a broken webhook before re-registering",{"type":50,"tag":73,"props":498,"children":500},{"id":499},"workflow",[501],{"type":56,"value":502},"Workflow",{"type":50,"tag":504,"props":505,"children":507},"h3",{"id":506},"step-1-locate-the-failing-item",[508],{"type":56,"value":509},"Step 1 — Locate the failing item",{"type":50,"tag":59,"props":511,"children":512},{},[513,515,520,522,527,529,534],{"type":56,"value":514},"If the user named a source, go straight to ",{"type":50,"tag":95,"props":516,"children":518},{"className":517},[],[519],{"type":56,"value":204},{"type":56,"value":521},". Otherwise start with\n",{"type":50,"tag":95,"props":523,"children":525},{"className":524},[],[526],{"type":56,"value":187},{"type":56,"value":528}," and ",{"type":50,"tag":95,"props":530,"children":532},{"className":531},[],[533],{"type":56,"value":221},{"type":56,"value":535}," to find what's red.",{"type":50,"tag":59,"props":537,"children":538},{},[539],{"type":56,"value":540},"Two kinds of failure:",{"type":50,"tag":80,"props":542,"children":543},{},[544,562],{"type":50,"tag":84,"props":545,"children":546},{},[547,552,554,560],{"type":50,"tag":65,"props":548,"children":549},{},[550],{"type":56,"value":551},"Source-level",{"type":56,"value":553}," (",{"type":50,"tag":95,"props":555,"children":557},{"className":556},[],[558],{"type":56,"value":559},"ExternalDataSource.status = \"Error\"",{"type":56,"value":561},"): the connection itself is broken — credentials expired,\nhost unreachable, account disabled. Affects every table.",{"type":50,"tag":84,"props":563,"children":564},{},[565,570,572,577,579,585,587,593,595,601,603,609,611,617,618,624],{"type":50,"tag":65,"props":566,"children":567},{},[568],{"type":56,"value":569},"Schema-level",{"type":56,"value":571}," — the source connects fine but one or more tables are failing. In the serialized API response\nfrom ",{"type":50,"tag":95,"props":573,"children":575},{"className":574},[],[576],{"type":56,"value":221},{"type":56,"value":578},", look for ",{"type":50,"tag":95,"props":580,"children":582},{"className":581},[],[583],{"type":56,"value":584},"status",{"type":56,"value":586}," values ",{"type":50,"tag":95,"props":588,"children":590},{"className":589},[],[591],{"type":56,"value":592},"\"Failed\"",{"type":56,"value":594},", ",{"type":50,"tag":95,"props":596,"children":598},{"className":597},[],[599],{"type":56,"value":600},"\"Billing limits\"",{"type":56,"value":602},", or ",{"type":50,"tag":95,"props":604,"children":606},{"className":605},[],[607],{"type":56,"value":608},"\"Billing limits too low\"",{"type":56,"value":610},". (The underlying model enum values are ",{"type":50,"tag":95,"props":612,"children":614},{"className":613},[],[615],{"type":56,"value":616},"BillingLimitReached",{"type":56,"value":528},{"type":50,"tag":95,"props":619,"children":621},{"className":620},[],[622],{"type":56,"value":623},"BillingLimitTooLow",{"type":56,"value":625},", but the\nserializer rewrites them — match on both the human-readable and enum forms to be safe.)",{"type":50,"tag":59,"props":627,"children":628},{},[629,631,636,638,644],{"type":56,"value":630},"A source can look ",{"type":50,"tag":95,"props":632,"children":634},{"className":633},[],[635],{"type":56,"value":118},{"type":56,"value":637}," at the top level while one of its schemas is ",{"type":50,"tag":95,"props":639,"children":641},{"className":640},[],[642],{"type":56,"value":643},"Failed",{"type":56,"value":645}," — always check both.",{"type":50,"tag":504,"props":647,"children":649},{"id":648},"step-2-classify-the-schema-status",[650],{"type":56,"value":651},"Step 2 — Classify the schema status",{"type":50,"tag":59,"props":653,"children":654},{},[655,657,662,664,669],{"type":56,"value":656},"From ",{"type":50,"tag":95,"props":658,"children":660},{"className":659},[],[661],{"type":56,"value":221},{"type":56,"value":663},", each schema has a ",{"type":50,"tag":95,"props":665,"children":667},{"className":666},[],[668],{"type":56,"value":584},{"type":56,"value":670},":",{"type":50,"tag":149,"props":672,"children":673},{},[674,695],{"type":50,"tag":153,"props":675,"children":676},{},[677],{"type":50,"tag":157,"props":678,"children":679},{},[680,685,690],{"type":50,"tag":161,"props":681,"children":682},{},[683],{"type":56,"value":684},"Status",{"type":50,"tag":161,"props":686,"children":687},{},[688],{"type":56,"value":689},"Meaning",{"type":50,"tag":161,"props":691,"children":692},{},[693],{"type":56,"value":694},"Usually means",{"type":50,"tag":172,"props":696,"children":697},{},[698,719,740,767,797,828],{"type":50,"tag":157,"props":699,"children":700},{},[701,709,714],{"type":50,"tag":179,"props":702,"children":703},{},[704],{"type":50,"tag":95,"props":705,"children":707},{"className":706},[],[708],{"type":56,"value":100},{"type":50,"tag":179,"props":710,"children":711},{},[712],{"type":56,"value":713},"Sync currently executing",{"type":50,"tag":179,"props":715,"children":716},{},[717],{"type":56,"value":718},"Normal, unless stuck for hours",{"type":50,"tag":157,"props":720,"children":721},{},[722,730,735],{"type":50,"tag":179,"props":723,"children":724},{},[725],{"type":50,"tag":95,"props":726,"children":728},{"className":727},[],[729],{"type":56,"value":118},{"type":50,"tag":179,"props":731,"children":732},{},[733],{"type":56,"value":734},"Last sync finished successfully",{"type":50,"tag":179,"props":736,"children":737},{},[738],{"type":56,"value":739},"Healthy",{"type":50,"tag":157,"props":741,"children":742},{},[743,751,762],{"type":50,"tag":179,"props":744,"children":745},{},[746],{"type":50,"tag":95,"props":747,"children":749},{"className":748},[],[750],{"type":56,"value":643},{"type":50,"tag":179,"props":752,"children":753},{},[754,756],{"type":56,"value":755},"Last sync errored — see ",{"type":50,"tag":95,"props":757,"children":759},{"className":758},[],[760],{"type":56,"value":761},"latest_error",{"type":50,"tag":179,"props":763,"children":764},{},[765],{"type":56,"value":766},"Needs diagnosis",{"type":50,"tag":157,"props":768,"children":769},{},[770,779,792],{"type":50,"tag":179,"props":771,"children":772},{},[773],{"type":50,"tag":95,"props":774,"children":776},{"className":775},[],[777],{"type":56,"value":778},"Paused",{"type":50,"tag":179,"props":780,"children":781},{},[782,784,790],{"type":56,"value":783},"User disabled sync (",{"type":50,"tag":95,"props":785,"children":787},{"className":786},[],[788],{"type":56,"value":789},"should_sync = false",{"type":56,"value":791},")",{"type":50,"tag":179,"props":793,"children":794},{},[795],{"type":56,"value":796},"Intentional",{"type":50,"tag":157,"props":798,"children":799},{},[800,818,823],{"type":50,"tag":179,"props":801,"children":802},{},[803,809,811,816],{"type":50,"tag":95,"props":804,"children":806},{"className":805},[],[807],{"type":56,"value":808},"Billing limits",{"type":56,"value":810}," (serializer) \u002F ",{"type":50,"tag":95,"props":812,"children":814},{"className":813},[],[815],{"type":56,"value":616},{"type":56,"value":817}," (enum)",{"type":50,"tag":179,"props":819,"children":820},{},[821],{"type":56,"value":822},"Team hit its warehouse row quota",{"type":50,"tag":179,"props":824,"children":825},{},[826],{"type":56,"value":827},"Billing issue, not a technical failure",{"type":50,"tag":157,"props":829,"children":830},{},[831,847,852],{"type":50,"tag":179,"props":832,"children":833},{},[834,840,841,846],{"type":50,"tag":95,"props":835,"children":837},{"className":836},[],[838],{"type":56,"value":839},"Billing limits too low",{"type":56,"value":810},{"type":50,"tag":95,"props":842,"children":844},{"className":843},[],[845],{"type":56,"value":623},{"type":56,"value":817},{"type":50,"tag":179,"props":848,"children":849},{},[850],{"type":56,"value":851},"Team has insufficient credit",{"type":50,"tag":179,"props":853,"children":854},{},[855],{"type":56,"value":856},"Billing issue",{"type":50,"tag":59,"props":858,"children":859},{},[860,862,868,870,875,877,882,884,889],{"type":56,"value":861},"Always check ",{"type":50,"tag":95,"props":863,"children":865},{"className":864},[],[866],{"type":56,"value":867},"last_synced_at",{"type":56,"value":869}," alongside status. A schema in ",{"type":50,"tag":95,"props":871,"children":873},{"className":872},[],[874],{"type":56,"value":100},{"type":56,"value":876}," with ",{"type":50,"tag":95,"props":878,"children":880},{"className":879},[],[881],{"type":56,"value":867},{"type":56,"value":883}," from 12 hours ago is\nalmost certainly stuck, even though the status isn't ",{"type":50,"tag":95,"props":885,"children":887},{"className":886},[],[888],{"type":56,"value":643},{"type":56,"value":890},".",{"type":50,"tag":504,"props":892,"children":894},{"id":893},"step-3-interpret-latest_error",[895,897],{"type":56,"value":896},"Step 3 — Interpret ",{"type":50,"tag":95,"props":898,"children":900},{"className":899},[],[901],{"type":56,"value":761},{"type":50,"tag":59,"props":903,"children":904},{},[905,907,912],{"type":56,"value":906},"Map the ",{"type":50,"tag":95,"props":908,"children":910},{"className":909},[],[911],{"type":56,"value":761},{"type":56,"value":913}," string to a root cause. Common patterns:",{"type":50,"tag":149,"props":915,"children":916},{},[917,938],{"type":50,"tag":153,"props":918,"children":919},{},[920],{"type":50,"tag":157,"props":921,"children":922},{},[923,928,933],{"type":50,"tag":161,"props":924,"children":925},{},[926],{"type":56,"value":927},"Error substring",{"type":50,"tag":161,"props":929,"children":930},{},[931],{"type":56,"value":932},"Root cause",{"type":50,"tag":161,"props":934,"children":935},{},[936],{"type":56,"value":937},"Fix",{"type":50,"tag":172,"props":939,"children":940},{},[941,996,1018,1060,1088,1110,1152,1174,1217,1261],{"type":50,"tag":157,"props":942,"children":943},{},[944,974,979],{"type":50,"tag":179,"props":945,"children":946},{},[947,953,954,960,961,967,968],{"type":50,"tag":95,"props":948,"children":950},{"className":949},[],[951],{"type":56,"value":952},"authentication failed",{"type":56,"value":594},{"type":50,"tag":95,"props":955,"children":957},{"className":956},[],[958],{"type":56,"value":959},"401",{"type":56,"value":594},{"type":50,"tag":95,"props":962,"children":964},{"className":963},[],[965],{"type":56,"value":966},"403",{"type":56,"value":594},{"type":50,"tag":95,"props":969,"children":971},{"className":970},[],[972],{"type":56,"value":973},"invalid credentials",{"type":50,"tag":179,"props":975,"children":976},{},[977],{"type":56,"value":978},"Credentials expired or rotated",{"type":50,"tag":179,"props":980,"children":981},{},[982,984,989,991],{"type":56,"value":983},"User rotates creds, then ",{"type":50,"tag":95,"props":985,"children":987},{"className":986},[],[988],{"type":56,"value":347},{"type":56,"value":990}," with new ",{"type":50,"tag":95,"props":992,"children":994},{"className":993},[],[995],{"type":56,"value":358},{"type":50,"tag":157,"props":997,"children":998},{},[999,1008,1013],{"type":50,"tag":179,"props":1000,"children":1001},{},[1002],{"type":50,"tag":95,"props":1003,"children":1005},{"className":1004},[],[1006],{"type":56,"value":1007},"Could not establish session to SSH gateway",{"type":50,"tag":179,"props":1009,"children":1010},{},[1011],{"type":56,"value":1012},"SSH tunnel misconfigured or remote host down",{"type":50,"tag":179,"props":1014,"children":1015},{},[1016],{"type":56,"value":1017},"User checks SSH host\u002Fkey\u002Fbastion",{"type":50,"tag":157,"props":1019,"children":1020},{},[1021,1030,1049],{"type":50,"tag":179,"props":1022,"children":1023},{},[1024],{"type":50,"tag":95,"props":1025,"children":1027},{"className":1026},[],[1028],{"type":56,"value":1029},"Primary key required for incremental syncs",{"type":50,"tag":179,"props":1031,"children":1032},{},[1033,1035,1041,1043],{"type":56,"value":1034},"Table has no PK and sync_type is ",{"type":50,"tag":95,"props":1036,"children":1038},{"className":1037},[],[1039],{"type":56,"value":1040},"incremental",{"type":56,"value":1042},"\u002F",{"type":50,"tag":95,"props":1044,"children":1046},{"className":1045},[],[1047],{"type":56,"value":1048},"cdc",{"type":50,"tag":179,"props":1050,"children":1051},{},[1052,1054],{"type":56,"value":1053},"Either add PK in source, or switch schema to ",{"type":50,"tag":95,"props":1055,"children":1057},{"className":1056},[],[1058],{"type":56,"value":1059},"full_refresh",{"type":50,"tag":157,"props":1061,"children":1062},{},[1063,1072,1077],{"type":50,"tag":179,"props":1064,"children":1065},{},[1066],{"type":50,"tag":95,"props":1067,"children":1069},{"className":1068},[],[1070],{"type":56,"value":1071},"primary keys for this table are not unique",{"type":50,"tag":179,"props":1073,"children":1074},{},[1075],{"type":56,"value":1076},"Declared PK columns aren't actually unique",{"type":50,"tag":179,"props":1078,"children":1079},{},[1080,1082],{"type":56,"value":1081},"Pick different PK columns via ",{"type":50,"tag":95,"props":1083,"children":1085},{"className":1084},[],[1086],{"type":56,"value":1087},"partial-update",{"type":50,"tag":157,"props":1089,"children":1090},{},[1091,1100,1105],{"type":50,"tag":179,"props":1092,"children":1093},{},[1094],{"type":50,"tag":95,"props":1095,"children":1097},{"className":1096},[],[1098],{"type":56,"value":1099},"Integration matching query does not exist",{"type":50,"tag":179,"props":1101,"children":1102},{},[1103],{"type":56,"value":1104},"Source's saved integration was deleted",{"type":50,"tag":179,"props":1106,"children":1107},{},[1108],{"type":56,"value":1109},"Recreate the source",{"type":50,"tag":157,"props":1111,"children":1112},{},[1113,1129,1134],{"type":50,"tag":179,"props":1114,"children":1115},{},[1116,1122,1123],{"type":50,"tag":95,"props":1117,"children":1119},{"className":1118},[],[1120],{"type":56,"value":1121},"column \"X\" does not exist",{"type":56,"value":594},{"type":50,"tag":95,"props":1124,"children":1126},{"className":1125},[],[1127],{"type":56,"value":1128},"does not have a column named",{"type":50,"tag":179,"props":1130,"children":1131},{},[1132],{"type":56,"value":1133},"Schema drift — incremental field or tracked column removed",{"type":50,"tag":179,"props":1135,"children":1136},{},[1137,1139,1145,1147],{"type":56,"value":1138},"Use ",{"type":50,"tag":95,"props":1140,"children":1142},{"className":1141},[],[1143],{"type":56,"value":1144},"incremental-fields-create",{"type":56,"value":1146}," to re-detect, then ",{"type":50,"tag":95,"props":1148,"children":1150},{"className":1149},[],[1151],{"type":56,"value":1087},{"type":50,"tag":157,"props":1153,"children":1154},{},[1155,1164,1169],{"type":50,"tag":179,"props":1156,"children":1157},{},[1158],{"type":50,"tag":95,"props":1159,"children":1161},{"className":1160},[],[1162],{"type":56,"value":1163},"relation \"...\" does not exist",{"type":50,"tag":179,"props":1165,"children":1166},{},[1167],{"type":56,"value":1168},"Source table was dropped\u002Frenamed",{"type":50,"tag":179,"props":1170,"children":1171},{},[1172],{"type":56,"value":1173},"Remove schema or rename source-side",{"type":50,"tag":157,"props":1175,"children":1176},{},[1177,1207,1212],{"type":50,"tag":179,"props":1178,"children":1179},{},[1180,1186,1187,1193,1194,1200,1201],{"type":50,"tag":95,"props":1181,"children":1183},{"className":1182},[],[1184],{"type":56,"value":1185},"SSL",{"type":56,"value":594},{"type":50,"tag":95,"props":1188,"children":1190},{"className":1189},[],[1191],{"type":56,"value":1192},"connection refused",{"type":56,"value":594},{"type":50,"tag":95,"props":1195,"children":1197},{"className":1196},[],[1198],{"type":56,"value":1199},"timeout",{"type":56,"value":594},{"type":50,"tag":95,"props":1202,"children":1204},{"className":1203},[],[1205],{"type":56,"value":1206},"unreachable",{"type":50,"tag":179,"props":1208,"children":1209},{},[1210],{"type":56,"value":1211},"Network \u002F firewall \u002F host reachability",{"type":50,"tag":179,"props":1213,"children":1214},{},[1215],{"type":56,"value":1216},"User side — check host\u002Fport\u002Fallowlist",{"type":50,"tag":157,"props":1218,"children":1219},{},[1220,1243,1248],{"type":50,"tag":179,"props":1221,"children":1222},{},[1223,1229,1230,1236,1237],{"type":50,"tag":95,"props":1224,"children":1226},{"className":1225},[],[1227],{"type":56,"value":1228},"replication slot",{"type":56,"value":594},{"type":50,"tag":95,"props":1231,"children":1233},{"className":1232},[],[1234],{"type":56,"value":1235},"publication",{"type":56,"value":594},{"type":50,"tag":95,"props":1238,"children":1240},{"className":1239},[],[1241],{"type":56,"value":1242},"wal_level",{"type":50,"tag":179,"props":1244,"children":1245},{},[1246],{"type":56,"value":1247},"CDC prerequisites broken",{"type":50,"tag":179,"props":1249,"children":1250},{},[1251,1253,1259],{"type":56,"value":1252},"Run ",{"type":50,"tag":95,"props":1254,"children":1256},{"className":1255},[],[1257],{"type":56,"value":1258},"check-cdc-prerequisites-create",{"type":56,"value":1260},"; may need slot recreate",{"type":50,"tag":157,"props":1262,"children":1263},{},[1264,1280,1285],{"type":50,"tag":179,"props":1265,"children":1266},{},[1267,1273,1274],{"type":50,"tag":95,"props":1268,"children":1270},{"className":1269},[],[1271],{"type":56,"value":1272},"Schema exceeds row limit",{"type":56,"value":594},{"type":50,"tag":95,"props":1275,"children":1277},{"className":1276},[],[1278],{"type":56,"value":1279},"billing",{"type":50,"tag":179,"props":1281,"children":1282},{},[1283],{"type":56,"value":1284},"Billing limit",{"type":50,"tag":179,"props":1286,"children":1287},{},[1288],{"type":56,"value":1289},"Upgrade plan or disable the schema",{"type":50,"tag":59,"props":1291,"children":1292},{},[1293,1295,1300,1302,1307],{"type":56,"value":1294},"If ",{"type":50,"tag":95,"props":1296,"children":1298},{"className":1297},[],[1299],{"type":56,"value":761},{"type":56,"value":1301}," is null but the schema is ",{"type":50,"tag":95,"props":1303,"children":1305},{"className":1304},[],[1306],{"type":56,"value":643},{"type":56,"value":1308},", retrieve the schema directly — the error may only be populated\non the detail view.",{"type":50,"tag":504,"props":1310,"children":1312},{"id":1311},"step-4-pick-the-recovery-action",[1313],{"type":56,"value":1314},"Step 4 — Pick the recovery action",{"type":50,"tag":59,"props":1316,"children":1317},{},[1318],{"type":56,"value":1319},"The recovery action depends on root cause, not just status. Match the user's situation to one of these:",{"type":50,"tag":59,"props":1321,"children":1322},{},[1323],{"type":50,"tag":65,"props":1324,"children":1325},{},[1326],{"type":56,"value":1327},"A. Transient failure (network blip, temporary API outage)",{"type":50,"tag":80,"props":1329,"children":1330},{},[1331,1336,1348],{"type":50,"tag":84,"props":1332,"children":1333},{},[1334],{"type":56,"value":1335},"Data synced so far is still valid.",{"type":50,"tag":84,"props":1337,"children":1338},{},[1339,1341,1346],{"type":56,"value":1340},"Action: ",{"type":50,"tag":95,"props":1342,"children":1344},{"className":1343},[],[1345],{"type":56,"value":279},{"type":56,"value":1347}," to retry using the configured sync method.",{"type":50,"tag":84,"props":1349,"children":1350},{},[1351],{"type":56,"value":1352},"Incremental\u002Fappend syncs pick up where they left off.",{"type":50,"tag":59,"props":1354,"children":1355},{},[1356],{"type":50,"tag":65,"props":1357,"children":1358},{},[1359],{"type":56,"value":1360},"B. Credentials expired or rotated",{"type":50,"tag":80,"props":1362,"children":1363},{},[1364,1369],{"type":50,"tag":84,"props":1365,"children":1366},{},[1367],{"type":56,"value":1368},"Every schema under the source is failing with an auth error.",{"type":50,"tag":84,"props":1370,"children":1371},{},[1372,1374,1379,1381,1386,1388,1393],{"type":56,"value":1373},"Action: user rotates creds → ",{"type":50,"tag":95,"props":1375,"children":1377},{"className":1376},[],[1378],{"type":56,"value":347},{"type":56,"value":1380}," with the new ",{"type":50,"tag":95,"props":1382,"children":1384},{"className":1383},[],[1385],{"type":56,"value":358},{"type":56,"value":1387}," → the reload happens\nautomatically when the source status flips back to running, or trigger manually with ",{"type":50,"tag":95,"props":1389,"children":1391},{"className":1390},[],[1392],{"type":56,"value":372},{"type":56,"value":890},{"type":50,"tag":59,"props":1395,"children":1396},{},[1397],{"type":50,"tag":65,"props":1398,"children":1399},{},[1400],{"type":56,"value":1401},"C. Schema drift — column renamed, dropped, or type changed",{"type":50,"tag":80,"props":1403,"children":1404},{},[1405,1410],{"type":50,"tag":84,"props":1406,"children":1407},{},[1408],{"type":56,"value":1409},"Error mentions a specific column that no longer matches the source.",{"type":50,"tag":84,"props":1411,"children":1412},{},[1413,1414,1419,1421,1426,1428,1434,1436,1442,1444,1450],{"type":56,"value":1340},{"type":50,"tag":95,"props":1415,"children":1417},{"className":1416},[],[1418],{"type":56,"value":423},{"type":56,"value":1420}," to get the current fields, then\n",{"type":50,"tag":95,"props":1422,"children":1424},{"className":1423},[],[1425],{"type":56,"value":330},{"type":56,"value":1427}," with the corrected ",{"type":50,"tag":95,"props":1429,"children":1431},{"className":1430},[],[1432],{"type":56,"value":1433},"incremental_field",{"type":56,"value":1435}," \u002F ",{"type":50,"tag":95,"props":1437,"children":1439},{"className":1438},[],[1440],{"type":56,"value":1441},"incremental_field_type",{"type":56,"value":1443}," \u002F\n",{"type":50,"tag":95,"props":1445,"children":1447},{"className":1446},[],[1448],{"type":56,"value":1449},"primary_key_columns",{"type":56,"value":1451},". Usually no need to wipe data.",{"type":50,"tag":59,"props":1453,"children":1454},{},[1455],{"type":50,"tag":65,"props":1456,"children":1457},{},[1458],{"type":56,"value":1459},"C2. Added \u002F renamed tables in the source database",{"type":50,"tag":80,"props":1461,"children":1462},{},[1463,1468],{"type":50,"tag":84,"props":1464,"children":1465},{},[1466],{"type":56,"value":1467},"User mentions \"I added a new table to Postgres but it isn't appearing\", or a source table was renamed.",{"type":50,"tag":84,"props":1469,"children":1470},{},[1471,1472,1477],{"type":56,"value":1340},{"type":50,"tag":95,"props":1473,"children":1475},{"className":1474},[],[1476],{"type":56,"value":389},{"type":56,"value":1478}," to pick up the new table list, then configure sync on any new\nschemas.",{"type":50,"tag":59,"props":1480,"children":1481},{},[1482],{"type":50,"tag":65,"props":1483,"children":1484},{},[1485],{"type":56,"value":1486},"D. Incremental state is wrong (duplicates, missing rows, data looks corrupt)",{"type":50,"tag":80,"props":1488,"children":1489},{},[1490,1502],{"type":50,"tag":84,"props":1491,"children":1492},{},[1493,1495,1500],{"type":56,"value":1494},"Schema status may be ",{"type":50,"tag":95,"props":1496,"children":1498},{"className":1497},[],[1499],{"type":56,"value":118},{"type":56,"value":1501}," — this isn't a \"failure\" per se, it's bad data.",{"type":50,"tag":84,"props":1503,"children":1504},{},[1505,1506,1511],{"type":56,"value":1340},{"type":50,"tag":95,"props":1507,"children":1509},{"className":1508},[],[1510],{"type":56,"value":296},{"type":56,"value":1512}," to wipe synced data and re-import from source. Destructive but often the\nright call for data-quality issues.",{"type":50,"tag":59,"props":1514,"children":1515},{},[1516],{"type":50,"tag":65,"props":1517,"children":1518},{},[1519],{"type":56,"value":1520},"E. CDC pipeline broken on Postgres",{"type":50,"tag":80,"props":1522,"children":1523},{},[1524,1529],{"type":50,"tag":84,"props":1525,"children":1526},{},[1527],{"type":56,"value":1528},"Error mentions replication slot, publication, WAL.",{"type":50,"tag":84,"props":1530,"children":1531},{},[1532,1533,1538,1540,1545,1547,1553],{"type":56,"value":1340},{"type":50,"tag":95,"props":1534,"children":1536},{"className":1535},[],[1537],{"type":56,"value":406},{"type":56,"value":1539}," to enumerate what's broken, fix on the Postgres\nside, then ",{"type":50,"tag":95,"props":1541,"children":1543},{"className":1542},[],[1544],{"type":56,"value":279},{"type":56,"value":1546},". If the WAL position was lost, a ",{"type":50,"tag":95,"props":1548,"children":1550},{"className":1549},[],[1551],{"type":56,"value":1552},"resync",{"type":56,"value":1554}," is sometimes unavoidable.",{"type":50,"tag":59,"props":1556,"children":1557},{},[1558],{"type":50,"tag":65,"props":1559,"children":1560},{},[1561,1563,1568],{"type":56,"value":1562},"F. Sync is stuck in ",{"type":50,"tag":95,"props":1564,"children":1566},{"className":1565},[],[1567],{"type":56,"value":100},{"type":56,"value":1569}," for hours",{"type":50,"tag":80,"props":1571,"children":1572},{},[1573,1592],{"type":50,"tag":84,"props":1574,"children":1575},{},[1576,1578,1583,1585,1590],{"type":56,"value":1577},"Check ",{"type":50,"tag":95,"props":1579,"children":1581},{"className":1580},[],[1582],{"type":56,"value":867},{"type":56,"value":1584},". If it's hours old and still ",{"type":50,"tag":95,"props":1586,"children":1588},{"className":1587},[],[1589],{"type":56,"value":100},{"type":56,"value":1591},", the job is orphaned.",{"type":50,"tag":84,"props":1593,"children":1594},{},[1595,1596,1601,1603,1608],{"type":56,"value":1340},{"type":50,"tag":95,"props":1597,"children":1599},{"className":1598},[],[1600],{"type":56,"value":255},{"type":56,"value":1602}," to stop it, then ",{"type":50,"tag":95,"props":1604,"children":1606},{"className":1605},[],[1607],{"type":56,"value":279},{"type":56,"value":890},{"type":50,"tag":59,"props":1610,"children":1611},{},[1612],{"type":50,"tag":65,"props":1613,"children":1614},{},[1615],{"type":56,"value":1616},"G. Table data is corrupt but you want to keep the schema config",{"type":50,"tag":80,"props":1618,"children":1619},{},[1620],{"type":50,"tag":84,"props":1621,"children":1622},{},[1623,1624,1629],{"type":56,"value":1340},{"type":50,"tag":95,"props":1625,"children":1627},{"className":1626},[],[1628],{"type":56,"value":313},{"type":56,"value":1630}," to drop the synced table but preserve the schema entry. Next reload\nre-imports from scratch without losing the configured sync_type\u002Fincremental_field.",{"type":50,"tag":59,"props":1632,"children":1633},{},[1634],{"type":50,"tag":65,"props":1635,"children":1636},{},[1637],{"type":56,"value":1638},"H. Billing limit",{"type":50,"tag":80,"props":1640,"children":1641},{},[1642],{"type":50,"tag":84,"props":1643,"children":1644},{},[1645],{"type":56,"value":1646},"Action isn't technical. Explain the limit, recommend upgrading the plan or disabling lower-priority schemas so the\nimportant ones fit under quota.",{"type":50,"tag":59,"props":1648,"children":1649},{},[1650],{"type":50,"tag":65,"props":1651,"children":1652},{},[1653],{"type":56,"value":1654},"I. Webhook-backed schema isn't receiving events",{"type":50,"tag":80,"props":1656,"children":1657},{},[1658,1678,1769],{"type":50,"tag":84,"props":1659,"children":1660},{},[1661,1663,1669,1671,1676],{"type":56,"value":1662},"Symptoms: schema has ",{"type":50,"tag":95,"props":1664,"children":1666},{"className":1665},[],[1667],{"type":56,"value":1668},"sync_type: \"webhook\"",{"type":56,"value":1670},", initial bulk sync finished, but no new rows arrive despite activity on\nthe source side. Status may still read ",{"type":50,"tag":95,"props":1672,"children":1674},{"className":1673},[],[1675],{"type":56,"value":118},{"type":56,"value":1677}," because the bulk sync (the safety-net cadence) is succeeding —\nthe problem is the push path.",{"type":50,"tag":84,"props":1679,"children":1680},{},[1681,1683],{"type":56,"value":1682},"Action:\n",{"type":50,"tag":1684,"props":1685,"children":1686},"ol",{},[1687,1697,1717,1737,1757],{"type":50,"tag":84,"props":1688,"children":1689},{},[1690,1696],{"type":50,"tag":95,"props":1691,"children":1693},{"className":1692},[],[1694],{"type":56,"value":1695},"external-data-sources-webhook-info-retrieve({source_id})",{"type":56,"value":890},{"type":50,"tag":84,"props":1698,"children":1699},{},[1700,1701,1707,1709,1715],{"type":56,"value":1294},{"type":50,"tag":95,"props":1702,"children":1704},{"className":1703},[],[1705],{"type":56,"value":1706},"exists: false",{"type":56,"value":1708}," → the webhook was never registered, or was deleted. Call ",{"type":50,"tag":95,"props":1710,"children":1712},{"className":1711},[],[1713],{"type":56,"value":1714},"create-webhook-create",{"type":56,"value":1716}," to\nregister it.",{"type":50,"tag":84,"props":1718,"children":1719},{},[1720,1721,1727,1729,1735],{"type":56,"value":1294},{"type":50,"tag":95,"props":1722,"children":1724},{"className":1723},[],[1725],{"type":56,"value":1726},"exists: true",{"type":56,"value":1728}," but ",{"type":50,"tag":95,"props":1730,"children":1732},{"className":1731},[],[1733],{"type":56,"value":1734},"external_status.error",{"type":56,"value":1736}," is set → typically \"API key doesn't have permission to read\nwebhooks\" or similar. The webhook may have been deleted on the source's dashboard. Re-create it.",{"type":50,"tag":84,"props":1738,"children":1739},{},[1740,1741,1747,1749,1755],{"type":56,"value":1294},{"type":50,"tag":95,"props":1742,"children":1744},{"className":1743},[],[1745],{"type":56,"value":1746},"external_status.status",{"type":56,"value":1748}," isn't ",{"type":50,"tag":95,"props":1750,"children":1752},{"className":1751},[],[1753],{"type":56,"value":1754},"\"enabled\"",{"type":56,"value":1756}," → the source disabled the webhook (usually after repeated\ndelivery failures). Re-enable or re-register.",{"type":50,"tag":84,"props":1758,"children":1759},{},[1760,1762,1768],{"type":56,"value":1761},"If payloads are arriving but failing signature verification → the signing secret was rotated. Get the new\none from the source's dashboard and call ",{"type":50,"tag":95,"props":1763,"children":1765},{"className":1764},[],[1766],{"type":56,"value":1767},"update-webhook-inputs-create({source_id}, {inputs: {signing_secret: \"...\"}})",{"type":56,"value":890},{"type":50,"tag":84,"props":1770,"children":1771},{},[1772],{"type":56,"value":1773},"After any fix, check the source's webhook logs (on their side) to confirm PostHog is now responding 2xx.",{"type":50,"tag":504,"props":1775,"children":1777},{"id":1776},"step-5-confirm-before-destructive-actions",[1778],{"type":56,"value":1779},"Step 5 — Confirm before destructive actions",{"type":50,"tag":59,"props":1781,"children":1782},{},[1783],{"type":56,"value":1784},"Three recovery actions discard data and cannot be undone:",{"type":50,"tag":80,"props":1786,"children":1787},{},[1788,1798,1808],{"type":50,"tag":84,"props":1789,"children":1790},{},[1791,1796],{"type":50,"tag":95,"props":1792,"children":1794},{"className":1793},[],[1795],{"type":56,"value":296},{"type":56,"value":1797}," — wipes synced rows, re-imports from scratch",{"type":50,"tag":84,"props":1799,"children":1800},{},[1801,1806],{"type":50,"tag":95,"props":1802,"children":1804},{"className":1803},[],[1805],{"type":56,"value":313},{"type":56,"value":1807}," — drops the synced table",{"type":50,"tag":84,"props":1809,"children":1810},{},[1811,1817],{"type":50,"tag":95,"props":1812,"children":1814},{"className":1813},[],[1815],{"type":56,"value":1816},"external-data-sources-destroy",{"type":56,"value":1818}," — deletes the source and all its schemas",{"type":50,"tag":59,"props":1820,"children":1821},{},[1822],{"type":56,"value":1823},"Always present the fix you're proposing and wait for explicit approval before calling any of these. \"Just try\nresync\" is rarely the right default.",{"type":50,"tag":73,"props":1825,"children":1827},{"id":1826},"example-interaction",[1828],{"type":56,"value":1829},"Example interaction",{"type":50,"tag":1831,"props":1832,"children":1837},"pre",{"className":1833,"code":1835,"language":56,"meta":1836},[1834],"language-text","User: \"Our Stripe sync is broken, can you check?\"\n\nAgent:\n- external-data-sources-list → find Stripe source, status = Error\n- external-data-sources-retrieve({id}) → latest_error: \"authentication failed: 401 Unauthorized\"\n- Report: \"Your Stripe source's API key is no longer authenticating.\n   All 8 tables under it are failing with 401s. This usually means the key was rotated on the Stripe side.\n\n   To fix:\n   1. Grab a fresh restricted API key from the Stripe dashboard.\n   2. I'll update the source with the new key.\n   3. Syncs will resume automatically — no data loss.\n\n   Paste the new key here when ready.\"\n\nUser: \"sk_live_...\"\n\nAgent:\n- external-data-sources-partial-update({id}, {job_inputs: {stripe_secret_key: \"sk_live_...\"}})\n- external-data-sources-reload({id}) to trigger retry\n- Report: \"Updated and re-triggered. Check back in a few minutes — latest_error should clear.\"\n","",[1838],{"type":50,"tag":95,"props":1839,"children":1840},{"__ignoreMap":1836},[1841],{"type":56,"value":1835},{"type":50,"tag":73,"props":1843,"children":1845},{"id":1844},"important-notes",[1846],{"type":56,"value":1847},"Important notes",{"type":50,"tag":80,"props":1849,"children":1850},{},[1851,1869,1920,1930,1962,1972],{"type":50,"tag":84,"props":1852,"children":1853},{},[1854,1859,1861,1867],{"type":50,"tag":65,"props":1855,"children":1856},{},[1857],{"type":56,"value":1858},"Source status overrides schema status for diagnosis.",{"type":56,"value":1860}," If the source is ",{"type":50,"tag":95,"props":1862,"children":1864},{"className":1863},[],[1865],{"type":56,"value":1866},"Error",{"type":56,"value":1868},", nothing under it will work;\nfixing the source usually fixes all its schemas at once.",{"type":50,"tag":84,"props":1870,"children":1871},{},[1872,1882,1884,1889,1891,1896,1898,1904,1906,1912,1914,1919],{"type":50,"tag":65,"props":1873,"children":1874},{},[1875,1880],{"type":50,"tag":95,"props":1876,"children":1878},{"className":1877},[],[1879],{"type":56,"value":100},{"type":56,"value":1881}," isn't always healthy.",{"type":56,"value":1883}," Cross-check ",{"type":50,"tag":95,"props":1885,"children":1887},{"className":1886},[],[1888],{"type":56,"value":867},{"type":56,"value":1890},". A sync stuck in ",{"type":50,"tag":95,"props":1892,"children":1894},{"className":1893},[],[1895],{"type":56,"value":100},{"type":56,"value":1897}," needs ",{"type":50,"tag":95,"props":1899,"children":1901},{"className":1900},[],[1902],{"type":56,"value":1903},"cancel",{"type":56,"value":1905}," then\n",{"type":50,"tag":95,"props":1907,"children":1909},{"className":1908},[],[1910],{"type":56,"value":1911},"reload",{"type":56,"value":1913},", not ",{"type":50,"tag":95,"props":1915,"children":1917},{"className":1916},[],[1918],{"type":56,"value":1552},{"type":56,"value":890},{"type":50,"tag":84,"props":1921,"children":1922},{},[1923,1928],{"type":50,"tag":65,"props":1924,"children":1925},{},[1926],{"type":56,"value":1927},"Resync is destructive.",{"type":56,"value":1929}," It discards synced data. Only recommend it when the data itself is bad (duplicates,\nmissing rows, corrupt) or when recovery genuinely requires a clean slate (lost WAL position on CDC). Never use it\nas a first-try for transient errors.",{"type":50,"tag":84,"props":1931,"children":1932},{},[1933,1938,1940,1946,1948,1953,1955,1960],{"type":50,"tag":65,"props":1934,"children":1935},{},[1936],{"type":56,"value":1937},"Delete-data preserves config.",{"type":56,"value":1939}," When a user says \"I just want to start this table over from scratch\", prefer\n",{"type":50,"tag":95,"props":1941,"children":1943},{"className":1942},[],[1944],{"type":56,"value":1945},"delete-data",{"type":56,"value":1947}," + ",{"type":50,"tag":95,"props":1949,"children":1951},{"className":1950},[],[1952],{"type":56,"value":1911},{"type":56,"value":1954}," over ",{"type":50,"tag":95,"props":1956,"children":1958},{"className":1957},[],[1959],{"type":56,"value":1552},{"type":56,"value":1961}," + new schema entry — it keeps the configured sync_type \u002F incremental_field\n\u002F PK setup.",{"type":50,"tag":84,"props":1963,"children":1964},{},[1965,1970],{"type":50,"tag":65,"props":1966,"children":1967},{},[1968],{"type":56,"value":1969},"Billing limits aren't technical failures.",{"type":56,"value":1971}," Don't try to retry or reconfigure your way out. Route to billing.",{"type":50,"tag":84,"props":1973,"children":1974},{},[1975,1980,1982,1987,1989,1995,1997,2002],{"type":50,"tag":65,"props":1976,"children":1977},{},[1978],{"type":56,"value":1979},"Webhook failures can hide behind a green status.",{"type":56,"value":1981}," A webhook-type schema whose bulk fallback sync succeeded looks\n",{"type":50,"tag":95,"props":1983,"children":1985},{"className":1984},[],[1986],{"type":56,"value":118},{"type":56,"value":1988}," even when the push channel is broken. When users say \"my data is hours behind\" on a webhook schema,\ncall ",{"type":50,"tag":95,"props":1990,"children":1992},{"className":1991},[],[1993],{"type":56,"value":1994},"webhook-info-retrieve",{"type":56,"value":1996}," before looking at schema status. Webhook issues don't surface on\n",{"type":50,"tag":95,"props":1998,"children":2000},{"className":1999},[],[2001],{"type":56,"value":221},{"type":56,"value":890},{"items":2004,"total":2124},[2005,2022,2040,2057,2074,2088,2106],{"slug":2006,"name":2006,"fn":2007,"description":2008,"org":2009,"tags":2010,"stars":29,"repoUrl":30,"updatedAt":2021},"analyzing-experiment-session-replays","analyze session replays for PostHog experiments","Analyze session replay patterns across experiment variants to understand user behavior differences. Use when the user wants to see how users interact with different experiment variants, identify usability issues, compare behavior patterns between control and test groups, or get qualitative insights to complement quantitative experiment results.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[2011,2014,2017,2018],{"name":2012,"slug":2013,"type":13},"Analytics","analytics",{"name":2015,"slug":2016,"type":13},"Design","design",{"name":9,"slug":8,"type":13},{"name":2019,"slug":2020,"type":13},"User Research","user-research","2026-04-06T18:44:38.291781",{"slug":2023,"name":2023,"fn":2024,"description":2025,"org":2026,"tags":2027,"stars":29,"repoUrl":30,"updatedAt":2039},"assessing-heatmaps","analyze page heatmaps and suggest improvements","Assesses what a page's heatmap is telling you and recommends concrete changes. Pulls click \u002F rageclick \u002F scroll-depth data for a URL, names the hot elements by cross-referencing autocapture events on the same page, and can create a saved heatmap the user opens in PostHog, then summarizes the behavior and proposes improvements.\nTRIGGER when: user asks what a heatmap shows, why people aren't clicking something, where users rage-click, how far they scroll, what to change on a page based on heatmap\u002Fclick data, or to 'analyze\u002Fassess\u002Freview the heatmap' for a URL.\nDO NOT TRIGGER when: the user only wants to create a saved heatmap screenshot with no analysis (use heatmaps-saved-create directly), or is asking about session replay in general (use investigating-replay).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[2028,2029,2032,2033,2036],{"name":2012,"slug":2013,"type":13},{"name":2030,"slug":2031,"type":13},"Frontend","frontend",{"name":9,"slug":8,"type":13},{"name":2034,"slug":2035,"type":13},"Product Management","product-management",{"name":2037,"slug":2038,"type":13},"UX Design","ux-design","2026-06-05T07:40:43.37798",{"slug":2041,"name":2041,"fn":2042,"description":2043,"org":2044,"tags":2045,"stars":29,"repoUrl":30,"updatedAt":2056},"auditing-experiments-flags","audit PostHog experiments and feature flags","Audit PostHog experiments and feature flags for configuration issues, staleness, and best-practice violations. Read when the user asks to audit, health-check, or review experiments or feature flags, check flag hygiene, or verify experiment setup.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[2046,2049,2052,2053],{"name":2047,"slug":2048,"type":13},"Audit","audit",{"name":2050,"slug":2051,"type":13},"Feature Flags","feature-flags",{"name":9,"slug":8,"type":13},{"name":2054,"slug":2055,"type":13},"QA","qa","2026-04-06T18:44:30.657553",{"slug":2058,"name":2058,"fn":2059,"description":2060,"org":2061,"tags":2062,"stars":29,"repoUrl":30,"updatedAt":2073},"authoring-scouts","author and edit PostHog Signals scouts","How to author, edit, and adapt PostHog Signals scouts — the scheduled agents that scan a project and write reports into the Signals inbox. Use when a user wants to customize a canonical scout for their own setup (narrow its scope, retune its thresholds, add disqualifiers), tweak a scout's schedule or dry-run posture, or write a brand-new scout from scratch for a specific use case (a custom event, a product surface no canonical scout covers), or steer a scout without editing it at all by leaving it a note. Covers the scout SKILL.md anatomy, the report contract, the dedupe + scratchpad-memory conventions, the scout-notes steering channel, the per-team skills-store path vs the canonical in-repo path, and the write-and-inspect test loop (with dry-run as an optional safety net). Trigger on \"write\u002Fedit\u002Fcustomize a signals scout\", \"new scout for X\", \"tune my scout schedule\", \"make a scout that watches \u003Cevent>\", \"leave a note for \u002F give feedback to a scout\", \"tell the scouts about X\".\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[2063,2066,2069,2072],{"name":2064,"slug":2065,"type":13},"Agents","agents",{"name":2067,"slug":2068,"type":13},"Automation","automation",{"name":2070,"slug":2071,"type":13},"Observability","observability",{"name":9,"slug":8,"type":13},"2026-07-28T05:33:45.509154",{"slug":2075,"name":2075,"fn":2076,"description":2077,"org":2078,"tags":2079,"stars":29,"repoUrl":30,"updatedAt":2087},"building-a-dashboard","build and update PostHog dashboards","Build a new dashboard, or update an existing one, from a set of insights — the same job the in-app assistant does with its upsert-dashboard tool, but over MCP. Use when a user asks to create a dashboard, put several metrics\u002Fcharts together on one page, assemble a dashboard for a topic (product analytics, retention, revenue, activation, etc.), or add\u002Fremove\u002Freplace insights on a dashboard they already have. Covers deciding create vs update, reusing existing insights vs creating new ones, and using PostHog's vetted dashboard templates as reference for what a strong dashboard on a topic looks like.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[2080,2081,2084],{"name":2012,"slug":2013,"type":13},{"name":2082,"slug":2083,"type":13},"Dashboards","dashboards",{"name":2085,"slug":2086,"type":13},"MCP","mcp","2026-07-21T06:07:38.060598",{"slug":2089,"name":2089,"fn":2090,"description":2091,"org":2092,"tags":2093,"stars":29,"repoUrl":30,"updatedAt":2105},"checking-deploy-timing","correlate PostHog deployments with GitHub commits","Determine when a PostHog code change reached a given environment by reading the hidden GIT deploy annotations in the project and correlating them with the merge commit on GitHub. Use when PostHog staff ask \"when was X deployed\", \"is my change live in the US\u002FEU yet\", \"has my PR shipped\", \"did the fix roll out to prod-us\", or otherwise want to know whether\u002Fwhen a commit, PR, or feature went out to a region. Do not answer deploy-timing questions from event\u002Fdata volume alone — that only shows when data changed, not when code shipped.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[2094,2097,2100,2103,2104],{"name":2095,"slug":2096,"type":13},"Deployment","deployment",{"name":2098,"slug":2099,"type":13},"Git","git",{"name":2101,"slug":2102,"type":13},"GitHub","github",{"name":2070,"slug":2071,"type":13},{"name":9,"slug":8,"type":13},"2026-06-28T07:46:59.53536",{"slug":2107,"name":2107,"fn":2108,"description":2109,"org":2110,"tags":2111,"stars":29,"repoUrl":30,"updatedAt":2123},"choosing-trend-or-slope-view","visualize trends and growth over time","Clarify how to visualize change over a time range before building a trend. Use whenever the user asks how much something changed, grew, dropped, improved, or regressed between two points or periods — \"how much did X change from A to B\", \"before vs after\", \"start vs end\", \"week over week\", \"compare this month to last\", \"change over time\" — or mentions a \"slope chart\" \u002F \"slopegraph\". Two readings of \"change\" need different charts: the whole trend (a line, every interval) versus just the two endpoints (a slope, start vs end). Ask which they want, then render it. Not for choosing a saved insight ChartDisplayType in the insight editor.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[2112,2113,2116,2119,2120],{"name":2012,"slug":2013,"type":13},{"name":2114,"slug":2115,"type":13},"Charts","charts",{"name":2117,"slug":2118,"type":13},"Data Visualization","data-visualization",{"name":9,"slug":8,"type":13},{"name":2121,"slug":2122,"type":13},"Reporting","reporting","2026-06-18T08:18:57.960157",56,{"items":2126,"total":2278},[2127,2142,2152,2162,2175,2188,2202,2215,2227,2242,2252,2268],{"slug":2128,"name":2128,"fn":2129,"description":2130,"org":2131,"tags":2132,"stars":2139,"repoUrl":2140,"updatedAt":2141},"analyzing-expensive-users","analyze expensive users in AI observability","Analyze the most expensive users in AI observability and explain why they cost so much. Use when the user asks about top spenders, expensive users, per-user LLM cost, user-level cost drivers, or patterns behind high AI observability spend.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[2133,2134,2137,2138],{"name":2012,"slug":2013,"type":13},{"name":2135,"slug":2136,"type":13},"Cost Optimization","cost-optimization",{"name":2070,"slug":2071,"type":13},{"name":9,"slug":8,"type":13},35568,"https:\u002F\u002Fgithub.com\u002FPostHog\u002Fposthog","2026-07-28T05:34:11.117757",{"slug":2143,"name":2143,"fn":2144,"description":2145,"org":2146,"tags":2147,"stars":2139,"repoUrl":2140,"updatedAt":2151},"auditing-endpoints","audit PostHog project endpoints","Audit every endpoint in a PostHog project for staleness, failed materialisations, and unused materialised versions. Use when the user asks \"what endpoints can I clean up?\", \"are any of my endpoints broken?\", \"which materialised versions are still being called?\", or wants a one-shot cleanup pass over the Endpoints product. Produces a prioritised report grouped by issue type, with recommended actions but does not modify anything without explicit confirmation.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[2148,2149,2150],{"name":2012,"slug":2013,"type":13},{"name":2047,"slug":2048,"type":13},{"name":9,"slug":8,"type":13},"2026-06-08T08:08:33.693989",{"slug":134,"name":134,"fn":2153,"description":2154,"org":2155,"tags":2156,"stars":2139,"repoUrl":2140,"updatedAt":2161},"audit PostHog data warehouse source health","Audit the health of a PostHog project's data warehouse sources and syncs — find every broken or degraded source connection, sync schema, and webhook channel. Use when the user asks \"why are my imports failing?\", \"what's broken with my sources?\", \"why is my warehouse data stale?\", or wants a one-shot triage of source\u002Fsync health before deciding where to dig in. Produces a prioritized report grouped by severity, with recommended next steps. For materialized-view health use `auditing-warehouse-view-health`; for a single failing sync use `diagnosing-failed-warehouse-syncs`.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[2157,2158,2159,2160],{"name":2047,"slug":2048,"type":13},{"name":21,"slug":22,"type":13},{"name":2070,"slug":2071,"type":13},{"name":9,"slug":8,"type":13},"2026-06-18T08:22:57.67984",{"slug":2163,"name":2163,"fn":2164,"description":2165,"org":2166,"tags":2167,"stars":2139,"repoUrl":2140,"updatedAt":2174},"auditing-warehouse-view-health","audit PostHog materialized view health","Audit the health of a PostHog project's materialized views (saved queries) — find every failed materialization and flag unused or stale materialized views that cost storage and compute. Use when the user asks \"which of my views are broken?\", \"why is this materialized view failing?\", \"are any of my views wasting compute?\", or wants a one-shot triage of view health. For source\u002Fsync health use `auditing-warehouse-source-health`.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[2168,2169,2170,2173],{"name":2047,"slug":2048,"type":13},{"name":21,"slug":22,"type":13},{"name":2171,"slug":2172,"type":13},"Performance","performance",{"name":9,"slug":8,"type":13},"2026-06-18T08:25:10.936787",{"slug":2176,"name":2176,"fn":2177,"description":2178,"org":2179,"tags":2180,"stars":2139,"repoUrl":2140,"updatedAt":2187},"authoring-error-tracking-alerts","author PostHog error tracking alerts","Author error tracking alerts that fire when an issue is created, reopened, or starts spiking. Use when the user asks to set up error notifications, route exceptions to Slack\u002Fwebhook\u002FLinear, or evaluate which error events are worth alerting on. Covers trigger-event selection, integration choice, dedup against existing alerts, and shipping with the canonical message body shape.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[2181,2184,2185,2186],{"name":2182,"slug":2183,"type":13},"Alerting","alerting",{"name":27,"slug":28,"type":13},{"name":2070,"slug":2071,"type":13},{"name":9,"slug":8,"type":13},"2026-06-18T08:24:40.318583",{"slug":2189,"name":2189,"fn":2190,"description":2191,"org":2192,"tags":2193,"stars":2139,"repoUrl":2140,"updatedAt":2201},"authoring-log-alerts","author log alerts in PostHog","Author useful, low-noise log alerts on services in a PostHog project. Use when the user asks to set up alerts for their logs, suggest alerts they should add, or evaluate whether a service is worth monitoring. Covers service triage, baseline characterisation, threshold drafting, back-testing via simulate, and shipping with a notification destination.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[2194,2195,2196,2197,2200],{"name":2012,"slug":2013,"type":13},{"name":18,"slug":19,"type":13},{"name":2070,"slug":2071,"type":13},{"name":2198,"slug":2199,"type":13},"Operations","operations",{"name":9,"slug":8,"type":13},"2026-07-18T05:10:54.430898",{"slug":2203,"name":2203,"fn":2204,"description":2205,"org":2206,"tags":2207,"stars":2139,"repoUrl":2140,"updatedAt":2214},"building-workflows","build and edit PostHog workflows","Build, edit, test, enable, and monitor PostHog workflows over MCP. Author the action\u002Fedge graph so it runs and opens cleanly in the visual editor, then change drafts surgically with patch operations. Use when asked to build, set up, automate, change, fix, or debug a workflow, campaign, broadcast, drip sequence, or event-triggered automation in the workflows product.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[2208,2209,2210,2211],{"name":2067,"slug":2068,"type":13},{"name":2085,"slug":2086,"type":13},{"name":9,"slug":8,"type":13},{"name":2212,"slug":2213,"type":13},"Workflow Automation","workflow-automation","2026-07-28T05:34:12.167015",{"slug":2216,"name":2216,"fn":2217,"description":2218,"org":2219,"tags":2220,"stars":2139,"repoUrl":2140,"updatedAt":2226},"check-posthog-loading","inspect PostHog SDK loading across URLs","Inspect how the PostHog JavaScript SDK is loaded across a list of URLs. Use to confirm consistent installation across pages, find pages missing the snippet, detect mismatched API keys or hosts between pages, and verify the load method (head snippet vs deferred vs array.js).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[2221,2222,2223,2224,2225],{"name":2012,"slug":2013,"type":13},{"name":27,"slug":28,"type":13},{"name":2030,"slug":2031,"type":13},{"name":2070,"slug":2071,"type":13},{"name":9,"slug":8,"type":13},"2026-05-07T05:56:19.828048",{"slug":2228,"name":2228,"fn":2229,"description":2230,"org":2231,"tags":2232,"stars":2139,"repoUrl":2140,"updatedAt":2241},"consuming-endpoints-from-client-code","integrate PostHog endpoints into client applications","Wire a PostHog endpoint into a client app or SDK. Covers fetching the OpenAPI spec, generating a typed client with openapi-generator or @hey-api\u002Fopenapi-ts, sending the right auth header, shaping the variables payload (HogQL code_name vs insight breakdown property), handling rate-limit and materialised-endpoint error responses. Use when the user says \"how do I call my endpoint\", \"generate a client for this\", or \"what auth header do I use\".\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[2233,2236,2237,2238],{"name":2234,"slug":2235,"type":13},"API Development","api-development",{"name":2030,"slug":2031,"type":13},{"name":9,"slug":8,"type":13},{"name":2239,"slug":2240,"type":13},"SDK","sdk","2026-06-08T08:08:34.929454",{"slug":2243,"name":2243,"fn":2244,"description":2245,"org":2246,"tags":2247,"stars":2139,"repoUrl":2140,"updatedAt":2251},"copying-endpoints-across-projects","copy PostHog endpoints across projects","Copy a PostHog endpoint (a saved HogQL\u002Finsight query exposed as an API route) to another project in the same organization, or duplicate it under a new name in the same project. Use when the user wants to duplicate an endpoint, promote an endpoint from staging to production, replicate an endpoint's query\u002Fvariables\u002Ffreshness config in another workspace, or clone an endpoint to iterate on it. Unlike feature flags and experiments, endpoints have NO native cross-project copy tool — this skill covers the read-then-recreate flow (endpoint-get then endpoint-create), the active-project switching it requires, name-collision checks, and the safe defaults (land unmaterialised in the target, verify with endpoint-run). Does not cover editing endpoint versions (see managing-endpoint-versions) or authoring a brand-new endpoint from scratch (see creating-an-endpoint).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[2248,2249,2250],{"name":2234,"slug":2235,"type":13},{"name":2198,"slug":2199,"type":13},{"name":9,"slug":8,"type":13},"2026-07-15T05:29:58.442727",{"slug":2253,"name":2253,"fn":2254,"description":2255,"org":2256,"tags":2257,"stars":2139,"repoUrl":2140,"updatedAt":2267},"creating-ai-subscription","schedule recurring AI-generated PostHog reports","Create a recurring AI-generated PostHog report — schedule a free-text prompt to run on a cron, with the LLM-synthesized markdown delivered to email or Slack on each tick. Use when the user wants a recurring AI summary of X on any cadence (daily, weekly, monthly, yearly) rather than a one-off report. (To attach an AI summary to an existing insight\u002Fdashboard subscription instead of a free-text prompt, see `managing-subscriptions` and its `summary_enabled` option.)\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[2258,2259,2262,2263,2264],{"name":2067,"slug":2068,"type":13},{"name":2260,"slug":2261,"type":13},"Email","email",{"name":9,"slug":8,"type":13},{"name":2121,"slug":2122,"type":13},{"name":2265,"slug":2266,"type":13},"Slack","slack","2026-06-09T07:32:27.935712",{"slug":2269,"name":2269,"fn":2270,"description":2271,"org":2272,"tags":2273,"stars":2139,"repoUrl":2140,"updatedAt":2277},"creating-an-endpoint","create PostHog API endpoints","Create a PostHog endpoint with the right shape on the first try — covers query kind choice, name conventions, what to expose as variables (HogQL code_name vs insight breakdown), data_freshness_seconds, and whether to materialise on day one. Use when the user says \"create an endpoint\", \"expose this query as an API\", \"turn this insight into an endpoint\", or asks for help structuring a new endpoint. Steers away from common mistakes: materialising a query with cohort breakdowns or compare mode, inline-only variables on a materialised endpoint, unbounded date ranges, ambiguous names.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[2274,2275,2276],{"name":2012,"slug":2013,"type":13},{"name":2234,"slug":2235,"type":13},{"name":9,"slug":8,"type":13},"2026-06-08T08:08:29.624498",231]