Flexera One – ITAM – All Regions - Scheduled Report Execution Issues

We continue to work closely with the service provider to address the remaining scheduled report execution issue.

Based on recent log analysis, the behavior appears to be related to authentication handling during certain one-time report execution scenarios. Additional diagnostic logging is currently being implemented to further isolate the issue.

Recurring scheduled reports continue to function as expected. Further updates will be provided as additional findings are confirmed.

We remain actively engaged in ongoing investigation and remediation efforts to address the remaining scheduled report execution issue. Our teams are continuing to coordinate closely with the service provider to validate next steps and drive a long-term resolution.

Scheduled reports continue to function through standard recurring schedules, and reports remain accessible through the application.

Further updates will be shared as additional findings become available.

Our teams continue to work through the remaining scheduled report execution issue and are actively coordinating with the service provider to drive a long-term fix.

Recurring scheduled report delivery is functioning as expected. However, certain execution modes such as “Run Once” and “Run in Background” may still fail in some cases.

Customers are advised to configure reports using a standard recurring schedule for delivery by email or saving output to the portal as a temporary mitigation.

Scheduled report delivery configured on a recurring schedule has been functioning as expected following recent remediation and validation efforts.

The remaining issue is isolated to “Run Once” schedules and “Run in Background” executions, which may fail due to the way credentials are handled during one-time batch processing.

As a workaround, customers using “Run Once” or “Run in Background” are advised to create a standard recurring schedule to deliver report output by email or save it to the portal.

Investigation into the remaining behavior is ongoing, and further updates will be shared as additional findings become available.

We are continuing to work closely with our service provider as investigation continues into the remaining report execution behavior.

Recent validation confirms that recurring scheduled report delivery and email notifications are functioning as expected. However, additional testing has identified a remaining issue affecting “Run Once” and “Run in Background” report executions, which follow a different batch processing path.

Enhanced tracing has been enabled to support deeper analysis, and our teams are actively coordinating with the service provider to identify the underlying cause and implement a long-term resolution. Further updates will be shared as progress is confirmed.

We are continuing focused testing and validation as part of the ongoing remediation effort.

The latest round of tracing and diagnostic testing has been completed, and the results have been shared with our service provider for further review. We are currently awaiting their feedback and next steps based on the findings.

Access through the reporting portal remains available, and we will continue to monitor closely and provide further updates as progress is confirmed.

We are continuing focused investigation and testing in coordination with our service provider to address the remaining scheduling behavior.

As part of the next troubleshooting phase, additional diagnostic tracing has been enabled and testing is currently in progress to capture deeper execution details for review. These results will be used to support further analysis and drive a long-term resolution.

Access through the reporting portal remains available, and the environment continues to be actively monitored. Further updates will be shared as progress is confirmed.

We continue to work through the remaining scheduled reporting issue and are actively coordinating with our service provider to drive a permanent resolution.

At this time, recurring scheduled report delivery is functioning as expected, and reports remain accessible through the portal when run manually. Investigation is still ongoing into a specific execution path affecting “Run Once” and background-style report runs.

We have observed continued improvement and scheduled report delivery is now working as expected across environments.

Some customers may still see intermittent failures when running one-time scheduled reports or background executions. As a mitigation, users may need to renew their credentials so the system can pick up the updated authentication details for scheduled execution.

Our teams are actively coordinating with IBM to address this remaining behavior and confirm a long-term fix. We will continue monitoring closely and provide further updates as more information becomes available.

Recent remediation and testing efforts have resulted in scheduled reports running successfully across environments, with email notifications being delivered as expected. Our teams continue to monitor the platform closely to ensure this behavior remains consistent.

While core scheduled reporting functionality is currently operating as intended, we are maintaining a heightened monitoring state to watch for any recurrence and to complete follow-up analysis with our partners.

Our teams continue to actively work on this issue and remain fully engaged in coordination to deliver a durable, long-term fix. This remains a high-priority focus.

Ongoing investigation and testing have helped narrow the issue to the scheduled report execution path, which behaves differently from reports run directly within the application. Reports remain accessible through the portal, and validation work continues to ensure scheduled execution functions consistently across all environments.

The environment is being actively monitored as remediation efforts progress, including continued testing and review to confirm stability before broader changes are applied. Further updates will be shared as progress is confirmed.

We are continuing remediation and validation work to address the issue affecting scheduled report delivery. Configuration updates are being applied to ensure a consistent setup across environments, and additional testing is underway as part of this effort.

Our teams are actively monitoring results and coordinating next steps while further analysis continues. We will share another update once we have confirmed progress or received additional guidance.

Our teams have made progress as part of the ongoing remediation work. Recent testing has confirmed that scheduled report delivery is functioning as expected in a controlled test environment after applying updated configuration changes.

We are now proceeding with the same approach in additional environments, with focused testing underway to ensure consistent behavior before moving forward more broadly. Reports continue to run successfully when accessed directly through the reporting portal, and access remains available.

The environment is being actively monitored as this work continues. Further updates will be shared as progress is confirmed.

Our teams continue to work closely with the service provider to investigate the issue and identify a permanent solution. While reports are running successfully when executed on demand, scheduled executions continue to fail.

The business impact has been reiterated, as the issue has delayed production propagation and is now past due. The service provider has acknowledged this impact and is treating the issue as critical.

Our teams are continuing coordinated testing with the service provider to isolate the underlying root cause and implement a fix. Further updates will be shared as they become available.

Our teams are continuing to work on the remediation efforts. Recent testing and analysis are ongoing as part of this work, and updated configuration changes are being reviewed and validated in a controlled manner. Further updates will be shared as progress is confirmed.

We are continuing focused testing and validation in coordination with our service provider. Work is underway to apply updated configuration and verify behavior in a controlled manner before proceeding more broadly.

Access through the reporting portal remains available, and the environment is being actively monitored while this work continues. Further updates will be shared as progress is confirmed.

The investigation continues to be focused on the email connectivity mechanism used during scheduled report delivery. Additional testing has helped narrow down the likely root cause, and our teams are actively collaborating with the service provider to identify and implement an appropriate fix.

The issue has been escalated with the service provider for prioritized attention. Access to the reporting portal remains available, and our teams continue to closely monitor the environment while coordinating next steps to ensure a stable and sustainable resolution.

Recent testing has helped narrow the issue to the way scheduled reports are processed, which differs from reports run directly within the application. While reports continue to function when run manually, scheduled executions rely on additional system interactions that are not completing successfully.

Based on testing across environments and guidance from our service provider, the investigation is currently focused on how email connectivity is handled during scheduled report delivery, rather than the report content or underlying data. Changes applied in controlled environments have produced positive results, and further validation is ongoing before broader rollout.

Access to the reporting portal remains available, and teams are actively monitoring the environment and coordinating next steps to ensure a stable resolution.

We continue to monitor the environment closely while working with our service provider on the remaining scheduled report delivery issue. Recent validation efforts have highlighted consistent behavior across test environments, and additional data has been shared with the service provider to support further analysis.

Our teams continue to validate the fix and have identified some issues during testing. We are working closely with our service provider tto address these findings and refine the fix and restore the service to normalcy.

Recent testing in coordination with our service provider has helped identify the underlying cause of the scheduled report delivery issue. As part of this work, a configuration change was applied and validated during controlled testing, resulting in successful scheduled report email delivery.

Further testing and validation are currently underway to ensure the fix behaves as expected before broader rollout. We will continue to monitor closely and share updates as this work progresses.

Over the past several days, we have completed multiple rounds of remediation, testing, and validation in coordination with our service provider to address issues affecting scheduled Cognos reports.

Initial work resolved an earlier condition where scheduled reports were remaining stuck in a waiting state. Subsequent investigation confirmed that reports and dashboards continue to function correctly when run directly within the application. However, scheduled executions follow a different processing path, and failures are isolated to that scheduled execution flow.

Recent testing has focused on validating configuration, execution behavior, and data source resolution during scheduled runs. Additional diagnostic logging and traces have been enabled and reviewed to further narrow the cause, and testing continues based on guidance from the service provider.

Access to the reporting portal is available, and the environment is being actively monitored while this investigation progresses. We understand the importance of scheduled reporting and will continue to provide updates as further findings or remediation guidance becomes available.

Following the restoration of access, we continue to work closely with our service provider on the remaining scheduled report execution issue. Earlier remediation and validation efforts helped narrow the investigation to a specific scheduled execution scenario, and further analysis is ongoing to determine the appropriate resolution.

The environment is being actively monitored, and any regression will be addressed promptly.

Our teams worked closely with the service provider to resolve the accessibility issue. The US PROD environments are now accessible, and our teams have successfully verified access to reports and dashboards.

Our technical teams completed additional configuration testing and restarted the Cognos services in the US production environment. Despite these efforts, access to the reporting portal remains unavailable at this time, and users may be unable to log in to the Cognos portal.

A high-priority support case has been raised with the service provider for further investigation. Further updates will be shared as more information becomes available.

We are continuing testing and validation and are actively coordinating with our service provider as part of the ongoing investigation. Recent work has helped narrow the investigation to a specific scheduled execution path, and further analysis is underway to determine the appropriate resolution.

We recognize the importance of scheduled reporting for customers and appreciate your patience as this investigation continues. Additional updates will be shared once there is a meaningful change or new guidance to communicate.

Our teams are continuing to work with the service provider as part of the ongoing investigation. Additional diagnostic steps are being performed to support further analysis. We will provide further updates as soon as there is meaningful progress or new information is available.

Our teams remain engaged with our service provider and are progressing through additional review and testing. We will provide updates as soon as there is meaningful progress or new information to share.

Additional review and testing with our service provider are ongoing. In the meantime, reports remain accessible through the application and can be run manually while automated scheduled delivery continues to be investigated. Updates will be shared as meaningful progress or new guidance becomes available.

We continue to work closely with our service provider following additional review and testing. At this time, there is no immediate resolution, and investigation into the remaining issue affecting automated scheduled report delivery is ongoing.

Reports remain accessible through the application when run manually. Further updates will be shared as more information becomes available.

Additional diagnostic traces and logs have been collected and shared as part of the ongoing investigation with our service provider. Work is continuing to identify and address the remaining issue affecting automated scheduled report delivery.

Recent remediation steps have resolved an issue that was causing scheduled reports to remain stuck in a waiting state. Scheduled reports are now progressing past the queue stage; however, a separate execution-related issue is preventing automated report emails from being delivered successfully.

Investigation into this remaining issue is ongoing with the service provider. We will share further updates as progress continues.

We continue to work with our service provider as part of the ongoing remediation. Additional diagnostic information has been shared to support further investigation, and follow-up steps are being reviewed.

Automated scheduled report delivery is still not fully restored. Users can continue to access the application and run reports manually. We will share further updates as more information becomes available.

We have observed improvement following recent remediation steps; however, automated scheduled report delivery is not yet fully restored due to a separate execution issue identified during processing.

Users can continue to access the application and run reports manually. Further updates will be shared as remediation efforts continue.

Our teams applied the suggested configuration changes in the staging environment, but the issue persists. We are actively working with our service provider to continue the investigation and implement further remediation actions.

Our teams remain engaged, and the next remediation step is planned following recent configuration changes. Further updates will be shared once the next step has been executed.

We are diligently pursuing remediation efforts. The configuration changes implemented as part of the recovery process are currently in effect, and we are continuing with additional follow-up actions to resolve the issue impacting scheduled report email delivery.

Our teams are actively investigating the root cause and validating the necessary next steps to restore full functionality.
We will provide further updates as progress is made.

We are continuing remediation efforts and have implemented configuration changes as part of the recovery process. Additional follow-up work is currently in progress to restore scheduled report email delivery.

Some customers may continue to experience delays or non-delivery of scheduled report emails during this time.

We will provide further updates as work continues.

We are continuing to investigate an issue affecting the delivery of scheduled Cognos reports in the EU and NAM regions. While scheduled reports are running as expected, some customers may experience delays or non-delivery of report emails.

Our teams are actively working to identify the cause and restore normal email delivery. At this time, there is no impact to accessing reports directly within the application.

We will provide further updates as more information becomes available.

Incident Description: We have identified an issue affecting Flexera One IT Asset Management in the APAC, EU and NAM regions. The issue is preventing scheduled reports from being delivered as expected, which may result in customers not receiving automated reports during the impacted period.

Priority: P2

Restoration Activity: Our technical teams are actively investigating the issue and working to restore scheduled report delivery. Initial remediation actions did not resolve the issue. The teams are now working closely with the service provider to further investigate the root cause and implement a permanent fix.