Actions
Bug #6255
closedFirst access to rule page leads to "server can not be contacted at this time"
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
On recent 3.0 nightlies, the first time we go on the rule page we get a "server cannot be contacted at this time".
Seems to appears only with certains condition on the browser - it seems that something must be initialised, but if it was even in a distant past, it is OK.
Clearing cache on browser is not sufficient to bring it back.
Using a new URL for Rudder make it appears - so something cookies or local storage related ?
Actions