Why is FITS not working in one of my identical pipelines?

[arth...@gmail.com]

Hi all,
in addition to the problem noted here, I just discovered that one of the pipelines I manage doesn't use FITS and I don't understand why.

The Pipelines are all identical.
I checked and rechecked the processing configurations (default), they are identical.
In Preservation planning/Characterization Commands all commands are active, including FITS.
I even checked the fpr_fpcommand table of all MCP Servers, and as far as FITS is concerned, it is identical for all MCP Servers.

Yet, if I transfer&ingest an identical package, all pipelines run FITS except one; furthermore, the PREMIS sections with the FITS metadata extraction activity are clearly present in the generated METS files, except for that specific pipeline.

What am I missing?

Thanks in advance for any advice.

at