Appfire JMWE Outage History

Appfire JMWE is up right now

Appfire JMWE had 2 outages in the last 2 years totaling 122h 48m of downtime — averaging 0.1 incidents per month.

There were 2 Appfire JMWE outages since June 18, 2025 totaling 122h 48m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.innovalog.com

Notice December 1, 2025

Temporary interruption of Scheduled actions' execution

Detected by Pingoru
Dec 01, 2025, 09:52 AM UTC
Resolved
Nov 24, 2025, 12:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Dec 01, 2025, 09:52 AM UTC

    An issue in JMWE’s Scheduled Actions runner prevented some scheduled actions from triggering as intended. This incident occurred between Monday 12:00 UTC and Tuesday 19:00 UTC. Appfire team identified and resolved the root cause, restored normal functionality, and reran affected scheduled actions; however, as a result some executions may have occurred with delays or reduced frequency. We recommend that customers review their scheduled actions and manually rerun any that did not execute as intended.

Read the full incident report →

Minor June 18, 2025

Intermittent missing entries in JMWE Logs for some clients

Detected by Pingoru
Jun 18, 2025, 12:56 PM UTC
Resolved
Jun 23, 2025, 03:45 PM UTC
Duration
5d 2h
Affected: Log Service
Timeline · 6 updates
  1. 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.

  2. investigating Jun 18, 2025, 01:14 PM UTC

    We are continuing to investigate this issue.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

Read the full incident report →