UPGRADED TO V0.25.2 breaks parse document in dataset

[tradexsrl]

Hi , i just upraded to v0.25.2 but now when i try to reparse many existing document because i have modified the metadata , job are not working , i saw in the ragflow container log a loop of uknown job cancelled and never the classic output of page analyzed (ocr) with the metadata applied.
downgrading to v0.25.1 it solve the problem

[Ganesh-403]

@tradexsrl Since downgrading from v0.25.2 to v0.25.1 immediately resolves the issue, this doesn't sound like a metadata configuration problem. It points much more toward a regression introduced in v0.25.2.

A few things would help confirm that:

1. Does it happen with newly uploaded documents as well, or only when reparsing existing ones after changing metadata?
2. Do the worker logs contain any stack trace around the unknown job cancelled messages, or is that the only output?
3. Are you using the default ingestion pipeline or a custom one? v0.25 introduced the new ingestion pipeline, so it's worth ruling out whether the regression is pipeline-specific. :contentReference[oaicite:0]{index=0}

If the only log is repeatedly:

unknown job cancelled

and the normal OCR/parsing logs never appear, it suggests the parsing job is being cancelled before the document processing stage begins.

Given that:

• v0.25.1 parses successfully,
• v0.25.2 consistently fails on the same documents,
• and reverting the version fixes the problem,

I'd consider this strong evidence of a v0.25.2 regression rather than a deployment or metadata issue. I couldn't find any release note documenting a behavior change around reparsing documents with updated metadata in v0.25.2. :contentReference[oaicite:1]{index=1}

If you can share:

• the complete ragflow container log around the first unknown job cancelled,
• whether you're using OCR,
• and whether the problem affects all file types or only PDFs,

it would make it much easier for the maintainers to pinpoint the regression.

If this solves your problem, feel free to mark it as the accepted answer so others can find it easily.

[tradexsrl]

Hi , i upgraded to v0.25.6 some times ago and it solve the problem
thank's

[Ganesh-403]

alright