The report saved, the photo upload failed, and deleting the report looks like the clean way out. It is another write, so it can fail for the same reason the upload did, and the text the user typed is the one part that did save.
A FlutterFlow action chain is a sequence of separate writes to separate systems, and nothing rolls back the document Firestore already committed. Keep it, and make the retry safe instead. Create the submission ID before the first write, because Create Document generates a new one every run. Upload the photo to a fixed path. Store the ID and the step count in persisted App State so a restart resumes rather than starting over.
Then let the document's own fields decide the message. A report with submittedAt and no notifiedAt is submitted, not notified. Send Email only opens an email app, so the server is the only thing that can honestly claim the team was told.
https://www.duskolicanin.com/blog/flutterflow-action-chain-partial-failure