You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During census runs of 25k notifications we have noticed that the back end counts for processed notifications tend to be way in front of what the UI shows.
For example, if we search on "sanitized notifications" and divide by 2 to account for the fact that we duplicate log entries (another issue) we currently see 17000 Delivered notifications that are finished and processed in the db. Similarly if we search for "Updated notification" we see 3000 failures that are finished.
But when we look in the UI we see something like 11015 Delivered and 1705 Failed and it updates very very slowly whereas the back end is still steadily processing receipts at a good clip.
The text was updated successfully, but these errors were encountered:
During census runs of 25k notifications we have noticed that the back end counts for processed notifications tend to be way in front of what the UI shows.
For example, if we search on "sanitized notifications" and divide by 2 to account for the fact that we duplicate log entries (another issue) we currently see 17000 Delivered notifications that are finished and processed in the db. Similarly if we search for "Updated notification" we see 3000 failures that are finished.
But when we look in the UI we see something like 11015 Delivered and 1705 Failed and it updates very very slowly whereas the back end is still steadily processing receipts at a good clip.
The text was updated successfully, but these errors were encountered: