sorry, i had noticed that the monitoring was triggered a little while ago which indicates that its time to restart the frontend to mitigate this issue, but i forgot