Appfire JMWE incident
Intermittent missing entries in JMWE Logs for some clients
Appfire JMWE experienced a minor incident on June 18, 2025 affecting Log Service, lasting 5d 2h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 18, 2025, 12:56 PM UTC
We are currently investigating an issue where some clients may experience missing or delayed log entries in JMWE Logs. This may affect clients relying on JMWE Logs for recent execution records. Please note that the workflow execution itself is not impacted. We understand the importance of these logs for monitoring and troubleshooting workflows, and our engineering team is actively working to identify the root cause and restore functionality. We appreciate your patience and will provide updates as we learn more.
- investigating Jun 18, 2025, 01:14 PM UTC
We are continuing to investigate this issue.
- identified Jun 18, 2025, 02:15 PM UTC
We’ve identified the cause of the issue and are working on a fix. Thank you for your patience.
- identified Jun 18, 2025, 09:00 PM UTC
The fix has been implemented and is currently undergoing testing in our DTS environment before production rollout. Thank you for your continued patience.
- monitoring Jun 19, 2025, 10:55 AM UTC
Our team implemented a solution to address the issue affecting JMWE Logs. The fix has been deployed to production after successful testing, and we are currently monitoring the system to ensure stability. Thank you for your patience and understanding.
- resolved Jun 23, 2025, 03:45 PM UTC
After a few days of monitoring, no further issues have been observed. We are now resolving this incident. If you have any questions or encounter related issues, please don’t hesitate to contact our Support team. Thank you again for your patience.