Surface more internal state about offline entities #699
Labels
backend
Requires a change to the API server
enhancement
New feature or behavior
entities
Multiple Encounter workflows
frontend
Requires a change to the UI
v2024.2 adds limited information to Frontend about offline entities. We're not sure how common various edge cases will be, so it's not clear yet how important it is to surface additional information. This issue is to track ideas to surface additional information if/when that seems useful. See also #688, which is about doing more to surface entity errors (whether those errors are about offline entities or otherwise).
Idea 1: Show the offline entities backlog
When an offline update is in the backlog, it hasn't been applied yet. It may be helpful to users (and us!) to indicate that there have been changes that have not been applied yet. We could add a lean version of the backlog. I wrote on Slack:
Each row in the table could link to the submission, link to the entity if it exists, etc.
@lognaturel has pointed out that there are two pretty different situations in which an offline update ends up in the backlog:
We may want to surface (2), but it doesn't seem particularly helpful to surface (1). With that in mind, when showing the backlog, we could filter out submissions that have been in the backlog for less than a day.
Idea 2: Show more on the entity detail page about force-processing and missing submissions
There are a couple of ideas in this area. They have to do with showing more on the entity detail page when force-processing has already taken place for at least one update.
Idea 3: Show the submission being processed and held in the backlog on the submission detail page
There is no indication that a submission was processed and held in the backlog vs. not yet being processed. Maybe we want to show something in the submission activity feed when this happens? The reason against this is there are two extremes for a submission going into the backlog: 1) it's there for a few seconds while waiting for the submissions to get in the right order, in which case we probably don't need to show this or 2) it's stuck for a long time, possibly until it gets force-applied by the backlog processing cron job.
The text was updated successfully, but these errors were encountered: