Skip to content

Add DatasetResource.mark_failed for async fetch failures#89

Merged
koenvo merged 1 commit into
mainfrom
feat/mark-failed
Jul 8, 2026
Merged

Add DatasetResource.mark_failed for async fetch failures#89
koenvo merged 1 commit into
mainfrom
feat/mark-failed

Conversation

@koenvo

@koenvo koenvo commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

In the async submit/collect flow a source can now mark an individual DatasetResource as failed-to-fetch (dataset_resource.mark_failed(error)) and yield it from collect(). ingestify records it as a FAILED task without storing anything (no revision, so it is retried next run) instead of the failure being silently dropped. The failure is now visible in the ingestion job summary.

In the async submit/collect flow a source can now mark an individual
DatasetResource as failed-to-fetch (dataset_resource.mark_failed(error))
and yield it from collect(). ingestify records it as a FAILED task without
storing anything (no revision, so it is retried next run) instead of the
failure being silently dropped. The failure is now visible in the
ingestion job summary.

The FAILED task mirrors the operation that would have run: UPDATE when the
resource already had a dataset (a failed refetch), CREATE otherwise. A
failed fetch is never represented as a bad/failed dataset — the existing
dataset is left untouched and recovers on the next successful run, so the
existing fetch/retry behaviour keeps working.

Claude-Session: https://claude.ai/code/session_01B5EfLJqoafjW1FhvkxGSmg
@koenvo koenvo force-pushed the feat/mark-failed branch from b5c356e to e943851 Compare July 8, 2026 09:49
@koenvo koenvo merged commit d624428 into main Jul 8, 2026
13 checks passed
@koenvo koenvo deleted the feat/mark-failed branch July 8, 2026 09:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant