gbif/pipelines

Killed / failed ingestions that are removed cannot be reprocessed

Closed this issue · 1 comments

When a dataset processing fails or is deliberately killed (e.g. kill a yarn job) it appears "stuck" in the running ingestion monitor.
You can "Finish" it using the UI but afterward cannot then run a specific step to reprocess it - I suspect it's related to something like being in a state in the registry that blocks new runs.

muttcg commented

Fixed in #935