A network error does not always mean nothing was sent

A connection can fail before the service receives the photos or after acceptance while the response is returning. Avoid immediately recreating the same images as a new report just because an error appeared.

Use the original report

The planned history keeps in-progress and uncertain email attempts available for status checks. When acceptance can be confirmed, there is no need to submit the photos again. If the result remains uncertain, ask the recipient through another channel.

Separate rejection from uncertainty

A request stopped before handoff, such as an invalid address, differs from an unknown result after sending began. Follow the displayed state rather than repeatedly tapping send. V1 does not promise perfect duplicate prevention under every failure.

Custom POST requires receiver cooperation

A custom HTTP endpoint needs to recognize report IDs to avoid processing retries twice. Sending the same ID cannot force a receiving system to deduplicate it. The email service’s status check is not automatically available for arbitrary POST destinations.

Field checklist

  1. Review the original report before creating another.
  2. Check email acceptance or ask the recipient if the result is uncertain.
  3. Retry confirmed failures according to the displayed guidance.

Common question

Is duplicate delivery impossible?

No. When an outcome is unknown, check the status or recipient before submitting another copy.