The ingest run failed to persist candidate data due to a database schema mismatch:
HTTPStatusError: Client error '400 Bad Request' for url 'https://ltafdcsnvppvqyoclkod.supabase.co/rest/v1/discovery_runs?on_conflict=run_id'
Response: {"code":"PGRST204","details":null,"hint":null,"message":"Could not find the 'skipped_query_count' column of 'discovery_runs' in the schema cache"}
This suggests the database schema is out of sync with the application code. The discovery_runs table appears to be missing the skipped_query_count column that the application expects.
Next steps:
- Check if database migrations need to be applied
- Verify the schema version matches the application requirements
- Consider if this is blocking data persistence or just auxiliary logging
Review context
-
Run timestamp: 2026-05-18T08:08:14.877167+00:00
-
Run snapshot: state_repo/news_items/ingest/runs/2026-05-18T08-08-14-877167Z.json
-
Debug summary: state_repo/news_items/ingest/logs/2026-05-18T08-08-14-877167Z.summary.json
-
Debug log: state_repo/news_items/ingest/logs/2026-05-18T08-08-14-877167Z.json
-
Workflow run: https://github.com/DataHackIL/tfht_enforce_idx/actions/runs/26021317412
The ingest run failed to persist candidate data due to a database schema mismatch:
This suggests the database schema is out of sync with the application code. The
discovery_runstable appears to be missing theskipped_query_countcolumn that the application expects.Next steps:
Review context
Run timestamp:
2026-05-18T08:08:14.877167+00:00Run snapshot:
state_repo/news_items/ingest/runs/2026-05-18T08-08-14-877167Z.jsonDebug summary:
state_repo/news_items/ingest/logs/2026-05-18T08-08-14-877167Z.summary.jsonDebug log:
state_repo/news_items/ingest/logs/2026-05-18T08-08-14-877167Z.jsonWorkflow run: https://github.com/DataHackIL/tfht_enforce_idx/actions/runs/26021317412