BUG - lockout of processing when job succeeds but produces no products

[subagonsouth]

Description of the issue

I ran into an issue when getting the Lo L1B prostar product going in production. I had a bug in the code that caused the job to produce no products but not raise an exception. This resulted in a condition in the DB that locks out the ability to trigger reprocessing for that date/repoint.

The condition is that there is a record of a successful v001 Processing job for the select date/repoint, but no data product for that date/repoint in the ScienceFiles table. This makes batch starter identify the version for a reprocess as v001 but then see that an identical job has already been run, so it skips triggering of the job.

One way to avoid this in the future would be to raise an exception in the ProcessInstrument.post_processing() method if the processed_data parameter has length zero. The upshot is that we can't have any jobs that intentionally produce no output products.

Steps to reproduce the issue

No response

Expected behavior (What should happen)

No response

Actual behavior (What does happen)

No response

Code Snippet:

Code

Additional notes, affected areas, and suggested fixes

No response