On June 11th, from approximately 11:30 to 13:30, our NL3 hosting location experienced a major incident. After a redeployment of the action service, all messages related to automated actions remained in the queue without being delivered to the action service, which resulted in automated actions not being executed. In response, we restarted the action service on NL3. After a brief period where the action service caught up on executing all actions triggered after 11:30, the behavior of the automated action system went back to normal. While the exact root cause remains under investigation, this incident has provided invaluable insights. These insights are being used as a basis for ongoing improvement in our understanding and management of our messaging system. We are confident that with these insights, we will eventually be able to pinpoint the root cause of this incident with a high degree of certainty. We acknowledge these incidents as opportunities for systematic improvement and remain committed to leveraging this experience to ensure increased reliability and stability in our service.