When the Customized portals do not receive any access related events for a certain period, the browser where the Customized portals are hosted becomes inactive. The user needs to login again to the Customized portals to check the status of the received events.
To prevent frequent relogin, the autorefresh node has to be deployed in the main workspace area of the Rule editor where the flow is created.
The autorefresh node automatically reloads the Customized portals every few minutes.
