FYI - Check any ITAM API Custom Reports for Error

[johnksilverwood]

FYI - If you are using the reportsExecute method via the FlexeraOne ITAM API, you may want to double check your scripts.

I believe the upgrades or emergency maintenance from last week (personally I am in United States/North America flexeraOne) may have reset the setting that requires you to run the report once before it becomes visible to the API.

For example, on my existing reports that have been running fine already for months, here's the last error when querying:

"Cannot run the report, Either the reportID does not exist or retry after executing the report once in the UI"

After running the report in the UI, it's fine. I will check in with Flexera engineering too as it may be something they can reset on their side.

More context: Known Issue: Attempts to call the reportsExecute API fail after Flexera One ITAM maintenance with 40... - Community

[tjohnson1 · Accepted solution]

There was a failure with the task that runs at the end of upgrades to repopulate the underlying SQL for customer reports after the upgrade to 2023 R2.5 (https://status.flexera.com/incidents/dcr2dt2jgzxn) in NAM Production. The task has been rerun and all reports should now be available via the API without needing to be opened via the UI.