[Bug] Cutout downloads report as succeeded when no images are found

[djones1040]

🐞 Bug Report

The cutout stage is sometimes listed as successful even when no images exist.

Describe the bug

• The cutout stage should always be able to find at least one image, so when it doesn't that means something pathological happened. Simplest thing would be to mark these as failed and then they'll probably succeed when reprocessed.

---

Is this a regression?

---

To Reproduce

A couple examples:
https://blast.scimma.org/transients/2024gyh/
https://blast.scimma.org/transients/2024gwj/

---

Expected behaviour

---

Media prove

---

Your environment

• OS:
• Node version:
• Npm version:
• Browser name and version:

---

Additional context

[vlatada]

I fixed this bug by updating download_and_save_cutouts() to return the correct success/failure status when attempting to retrieve FITS images. The function now checks the status returned by cutout(), and if no image is downloaded (or an error occurs), it marks the task as “failed” instead of “processed.” This ensures the Cutout stage no longer reports success when no images were found.

[djones1040]

thank you!! so great to have this

[manning-ncsa]

@vlatada Where are your commits? Please push to your fork of this repo and open pull request.

[vlatada]

For some reason I'm not able push my commits to my fork I'm trying to figure this out right now

[vlatada]

Tasks:

• Define standards on what counts as a failure or success
• Report no images as its own state