Review and retry file uploads
Monitor's Data Ingestion view shows what happened to every uploaded file and every row in it, and processes the failed ones again.
A file uploaded for bulk enrollment is processed one row at a time, so a single row can fail while the rest of the file succeeds. Monitor → Data Ingestion shows what happened to each file and each of its rows, and offers to process the failed ones again.
A retry runs enrollment triggers a second time, which can start a second care flow for a patient who already has one.
Every file the organization uploaded is listed, newest first
The list covers all of the organization's buckets. Each file shows:
- File Name, Status and Uploaded At.
- Success Rate, Failure Rate and Warning Rate, each as a share of the file's rows. The success rate counts rows that succeeded and rows that were skipped.
- Total Records and Processing Time.
Filter by bucket, by file name, or by status: Processing, Completed, Failed or Delayed. A file name is matched exactly as typed. Sorting is by Uploaded At only.
A page holds 10, 20, 50 or 100 files, and paging stops at 10,000 files. Narrow the filters rather than paging to reach anything older than that.
A file's page carries its bucket, its enrollment triggers and its rows
Open a file from the list. The summary across the top gives its Source (the bucket it arrived in), the file name and size, Processing Results as counts of successful, failed, skipped and warning rows, and its Status, Processing Time and Processed At. A file that failed shows the error underneath.
Enrollment Triggers below that lists the triggers configured on the file's bucket, with each trigger's name, the care flow it affects, its action (Start Care Flow, Update Care Flow or Start Track) and whether it is enabled. A file that completed without processing a single row usually landed in a bucket that had no enrollment trigger on it at the time.
The file's rows come last, filterable by status (Processing, Completed, Failed, Warning, Delayed), by enrollment trigger, and by what a trigger did with the row (Success, Failure, Skipped).
The download link works without signing in
Clicking the file name opens the file in a new tab through a link valid for 24 hours. Anyone who has the link can download the file and the patient data in it, without signing in to Awell, so don't share it. To get help with a file, send Awell support the file name instead.
A retried file comes back as a new file, and only two kinds are offered one
The retry on a file's page is offered for two files:
- one whose processing failed, and
- one that completed without processing a single row, because its bucket had no enrollment trigger when the file arrived.
For anything else the button is disabled, and the tooltip says: "Only a file whose processing failed, or that completed without processing a row, can be processed again. Retry its failed rows instead."
A retry processes the file again as a new file, which appears in the files list under the same name. The original file and its page stay as they were.
Because every row is processed again, a row that already started a care flow before the file failed starts a second one. The exception is an enrollment trigger with Prevent duplicate enrollment turned on, which skips a patient who already has an active care flow of that definition. See Enrollment triggers.
A file is retried once. One that was already processed again says Already processed again and links to the copy; that copy is the file to look at, and to retry if it also failed.
A file that looks stuck is never offered a retry
Rows are processed at a few per second per organization, and a file shows no progress until it finishes. A large file, or one waiting behind another, can look unchanged for well over an hour and still be processing. Wait for it, or email support@awellhealth.com if it never completes.
A row is retried in place and runs all of its triggers again
On a row's page, the retry is offered for a row whose processing failed, and for one that ended in a warning because part of it failed. A row that completed, and a row still being processed, are refused; the tooltip says: "Only a row whose processing failed, wholly or in part, can be processed again."
A row retry updates that row; no new row is created. Every enrollment trigger on the row runs again, including the ones that already succeeded. Only Prevent duplicate enrollment stops a patient who already has an active care flow from getting a second one.
Reading the view and retrying a file need different permissions
Without permission to read patients' care flows, Data Ingestion shows "You don't have permission to view uploaded files. Ask an admin of your organization for a role that grants it." in place of any file.
Without permission to act on them, every page still reads normally and the retry is disabled, with the same message naming the retry rather than the read. See Team, roles and permissions for which roles grant what.
Next steps
Next: Debug integrations with Monitor — the rest of what Monitor covers, including incoming webhooks and the activities that failed.
Retry failed activities
Re-run failed API calls, calculations, EMR reports and extension actions from Monitor, and read what the retry did to each one.
Upgrade running care flows
Move care flows that are already running onto a newer published version of their care flow definition, one at a time or in bulk.