sync-debug

Run ntn workers sync status to check sync state, then ntn workers runs list to find failed runs, and ntn workers runs logs to read error output. Cross-reference the errors with your sync code in src/index.ts to identify the root cause.

Use ntn workers runs list --plain, filter by sync key with grep, take the first run ID, and pass it to ntn workers runs logs. This prints the full log output including stack traces and console.log statements from your sync code.

Authentication errors usually mean a missing or expired OAuth token or absent environment variables. Check tokens with ntn workers oauth token, verify variables with ntn workers env list, push missing vars with ntn workers env push, or re-authenticate via ntn workers oauth start.

An infinite loop happens when hasMore stays true because the cursor never advances. Verify that nextState changes between iterations and that your termination condition is actually reachable in the sync logic.

If the persisted state shape no longer matches your updated code, reset it with ntn workers sync state reset <key>. This clears the old state and triggers a full re-backfill from scratch.

Schema mismatches occur when property keys in your changes don't match the schema.properties definition, or when builder types don't align. Ensure Builder.title() pairs with Schema.title() and Builder.richText() with Schema.richText().