Re-runs a settled, non-success automation run so superadmins can act on
failures instead of only observing them.
RPA: re-derives the trigger inputs from the run's patient (via the same
validation service the manual sync button uses) and enqueues a fresh
CloudCruise run — the retry is a new rpa_runs row, never a mutation of the
failed one. Extend: re-signs the run's stored source PDF and resubmits it to
the same workflow; the new run is linked to the same originating RPA run.
Retry vs reprocess: patientCharts.reprocess is the canonical chart-keyed
resubmission (the doc-detail "Reprocess document" button). This run-keyed
mutation exists for runs that never produced a chart — failed/rejected
before ingest — where there is no chart to key on. When the run IS linked to
a chart, it delegates to the chart path so both surfaces share one
execution path.
Re-runs a settled, non-success automation run so superadmins can act on failures instead of only observing them.
RPA: re-derives the trigger inputs from the run's patient (via the same validation service the manual sync button uses) and enqueues a fresh CloudCruise run — the retry is a new
rpa_runsrow, never a mutation of the failed one. Extend: re-signs the run's stored source PDF and resubmits it to the same workflow; the new run is linked to the same originating RPA run.Retry vs reprocess:
patientCharts.reprocessis the canonical chart-keyed resubmission (the doc-detail "Reprocess document" button). This run-keyed mutation exists for runs that never produced a chart — failed/rejected before ingest — where there is no chart to key on. When the run IS linked to a chart, it delegates to the chart path so both surfaces share one execution path.