Actions
Bug #19064
open
After a webapp downtime, no compliance is visible for a long time
Status:
New
Priority:
N/A
Assignee:
Category:
Web - Compliance & node report
Target version:
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
First impressions of Rudder
Effort required:
Very Small
Priority:
0
Regression:
No
Description
After a webapp unavailability, when it is restarted, it will process reports in the order of arrival, which means it will process all previous reports, before being able to compute current compliance.
There is no indication in the interface or the logs, so the server just looks broken.
Updated by 
Updated by 
Updated by
Actions