Appfire JMWE Outage History

Appfire JMWE is up right now

Appfire JMWE had 9 outages in the last 2 years totaling 215h 28m of downtime — averaging 0.4 incidents per month.

There were 9 Appfire JMWE outages since June 5, 2024 totaling 215h 28m 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 →

Minor April 7, 2025

Limited Access to JMWE Configuration and Workflow Execution Issues After Upgrade

Detected by Pingoru
Apr 07, 2025, 01:31 PM UTC
Resolved
Apr 08, 2025, 10:54 AM UTC
Duration
21h 23m
Affected: JMWE for JIRA Cloud
Timeline · 4 updates
  1. investigating Apr 07, 2025, 01:31 PM UTC

    We are currently investigating an issue affecting some clients following the upgrade of JMWE from version 1.2.41 to 1.2.42. **** Impact: Clients experiencing this issue may be unable to access the JMWE configuration and settings pages. Additionally, workflow extensions and JMWE actions may not function as expected. **** Workaround: Re-installing the JMWE app has resolved the issue for some affected clients. If you are experiencing these symptoms, we recommend trying a re-install as a temporary solution. The issue has been reported to Atlassian, and we are working closely with them to identify the root cause and implement a permanent fix. We will provide updates as more information becomes available. Thank you for your patience.

  2. investigating Apr 07, 2025, 01:31 PM UTC

    We are continuing to investigate this issue.

  3. investigating Apr 07, 2025, 01:53 PM UTC

    We’ve identified a number of instances where the token signature is invalid. Reinstalling the app immediately resolves the issue. We’re currently investigating why these instances did not receive the new secret. This behavior appears to be related to Atlassian’s systems, and we’re working to get more clarity from their side.

  4. resolved Apr 08, 2025, 10:54 AM UTC

    Atlassian has resolved the issue. JMWE is now fully operational across all instances, and no further action — including reinstalling the app — is required. Thank you for your patience and understanding while we worked through this.

Read the full incident report →

Notice April 7, 2025

Intermittent Errors Due to Atlassian Platform Timeout Issues

Detected by Pingoru
Apr 07, 2025, 11:06 AM UTC
Resolved
Apr 07, 2025, 07:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 07, 2025, 11:06 AM UTC

    Between 7:00 AM UTC and 9:00 AM UTC, some users experienced intermittent 500 errors and functionality disruptions within the JMWE app. The issue was traced to upstream timeout errors originating from the Atlassian platform, which affected our app’s ability to communicate reliably with their services. Our development team replicated the issue and actively collaborated with Atlassian to investigate and resolve the problem. Atlassian has acknowledged the issue on their end and has since resolved the underlying cause. System logs now show a return to normal behavior, and our internal checks confirm that JMWE functionality has been restored. If any users continue to experience issues, performing a re-install of the app may help. We appreciate your patience while we worked with Atlassian to address this matter.

Read the full incident report →

Notice March 18, 2025

Event Based Actions are not working.

Detected by Pingoru
Mar 18, 2025, 08:33 AM UTC
Resolved
Mar 19, 2025, 04:17 PM UTC
Duration
1d 7h
Affected: JMWE for JIRA Cloud
Timeline · 7 updates
  1. identified Mar 18, 2025, 08:33 AM UTC

    Due to circumstances out of our control, the Event-Based Actions are not working. The issue has been escalated to Atlassian.

  2. identified Mar 18, 2025, 08:33 AM UTC

    We are continuing to work on a fix for this issue.

  3. identified Mar 18, 2025, 11:24 AM UTC

    Atlassian has acknowledged the issue and is working with their internal team and Appfire to resolve it.

  4. identified Mar 18, 2025, 02:42 PM UTC

    Atlassian has completed the necessary work based on the proposed solution and is now conducting an internal review. We will provide further updates as soon as we have more info.. Thank you for your patience.

  5. identified Mar 18, 2025, 04:37 PM UTC

    While Atlassian is still working on a definitive fix, in the meantime you can manually apply a fix that should resolve the issue by navigating to the Event Based Action page and clicking on 'Apply Fix'. In case you still notice any issues, please reach out to the Appfire Support Team. The 'Apply Fix' button will still remain visible until further notice. Thank you.

  6. monitoring Mar 19, 2025, 02:47 PM UTC

    Atlassian has implemented a fix. We will continue monitoring the situation for a while. Thank you for your patience.

  7. resolved Mar 19, 2025, 04:17 PM UTC

    Normal operations have resumed. We appreciate your patience while we resolved the issue. If you have any questions, please contact the Appfire Support Team. Thank you.

Read the full incident report →

Major March 10, 2025

Performance Degradation on JMWE Cloud

Detected by Pingoru
Mar 10, 2025, 11:11 AM UTC
Resolved
Mar 10, 2025, 11:59 AM UTC
Duration
48m
Affected: JMWE for JIRA Cloud
Timeline · 4 updates
  1. investigating Mar 10, 2025, 11:11 AM UTC

    We are currently experiencing performance degradation on the JMWE Cloud, which may result in delays or issues with workflow execution. Our team is actively investigating the root cause and working on a resolution. We will provide updates as soon as more information becomes available. Thank you for your patience.

  2. investigating Mar 10, 2025, 11:11 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Mar 10, 2025, 11:46 AM UTC

    The root cause of the performance degradation on the JMWE Cloud has been identified and addressed. We are currently monitoring the situation to ensure stability. We will provide a final update once the issue is fully resolved. Thank you for your patience.

  4. resolved Mar 10, 2025, 11:59 AM UTC

    The performance degradation on the JMWE Cloud has been successfully resolved. The root cause was identified and addressed, and after monitoring, we have confirmed that the system is now stable. Thank you for your patience and understanding. If you experience any further issues, please reach out to our support team.

Read the full incident report →

Major March 5, 2025

JMWE Scheduler Job Service - Performance Degradation

Detected by Pingoru
Mar 05, 2025, 02:10 AM UTC
Resolved
Mar 05, 2025, 08:43 AM UTC
Duration
6h 33m
Affected: JMWE for JIRA Cloud
Timeline · 4 updates
  1. investigating Mar 05, 2025, 02:10 AM UTC

    We are currently experiencing an issue with the JMWE Scheduler backend job service, which is impacting the performance of the configured Schedule Actions. Our team is investigating the root cause of the issue. Please note that all other JMWE functionalities remain fully operational. Thank you for your patience and understanding.

  2. identified Mar 05, 2025, 08:33 AM UTC

    JMWE Actions identified that were degrading the Scheduler’s backed job service. They have been isolated.

  3. monitoring Mar 05, 2025, 08:34 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Mar 05, 2025, 08:43 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 5, 2024

JMWE API down

Detected by Pingoru
Jun 05, 2024, 03:35 PM UTC
Resolved
Jun 06, 2024, 02:45 PM UTC
Duration
23h 9m
Affected: JMWE for JIRA Cloud
Timeline · 4 updates
  1. investigating Jun 05, 2024, 03:35 PM UTC

    JMWE API, which heavily relies on Jira Cloud API, has been rate-limited by Atlassian hence we are currently not able to serve requests. We are currently investigating the root cause of this issue working with Atlassian Support team to address it ASAP. We apologise for any inconvenience

  2. identified Jun 05, 2024, 03:37 PM UTC

    The issue has been identified and we are working with Atlassian to resolve it ASAP.

  3. monitoring Jun 05, 2024, 07:53 PM UTC

    After investigating with Atlassian we have ruled out issues on their side. To allow our customers to use JMWE once again we have rolled back to the previous version. In the meantime we keep monitoring the status of our infrastructure and developing a solution to this issue.

  4. resolved Jun 06, 2024, 02:45 PM UTC

    Unfortunately there has been a problem with the latest release (1.2.29-AC) that led us to roll back to the previous version. The issue is now resolved, and processing has resumed.

Read the full incident report →