We detected that the incident originated due to a service escalation problem, responsible for processing and distributing the agent status log and execution times, both agent inactivity triggers, as well as client and agent connection triggers. These incidents are currently solved.