topic Unable to see row count during reload when triggering reload without opening Data Load Editor (Qlik Cloud) in Management & Governance

Unable to see row count during reload when triggering reload without opening Data Load Editor (Qlik Cloud)

Qlik_Wizard — Wed, 11 Feb 2026 07:06:50 GMT

Hi Everyone,

I’m facing an issue in Qlik Sense and wanted to check if anyone else has experienced something similar.

Until the end of January 2026, I was able to see the number of rows being retrieved during app reloads. However, recently the reload progress no longer shows row counts and only displays the below message:

ReloadID: 698c03f89724c13c9f433ccc
Started loading data
(A detailed script progress log can be downloaded when the reload is finished)

Current behavior:

Reloading from the Data Load Editor works fine and displays the row counts as expected.
When I trigger a reload without opening the Data Load Editor (for example from the hub), it does not show the number of rows being retrieved.

Has anyone noticed a recent change in logging behavior or settings that might cause this?
Is there any configuration or permission update required to restore the detailed row-level progress during reload?

Any guidance or insights would be appreciated.

Thanks in advance!

Re: Unable to see row count during reload when triggering reload without opening Data Load Editor (Qlik Cloud)

Daniel_Castella — Thu, 12 Feb 2026 14:16:02 GMT

Hi @Qlik_Wizard

Yes, it is a planned change as described in the link:

The reload log payload is changing | Qlik Developer Portal

This change was a required step as Qlik modernizes the services that execute reloads and expands the capabilities of the Reload API. It lays the groundwork for a significantly richer reload monitoring experience, including more robust real-time visibility and improved troubleshooting features going forward. While these platform improvements are already helping some customers, it is known that they also disrupt established workflows for others.

In Technical Support team, we have received some cases about this topic, and all this feedback is currently being shared directly with our R&D and engine teams as they continue shaping the next iteration of reload monitoring. Qlik goal is not to reduce transparency, but to deliver a more powerful and reliable monitoring experience than what was previously available.

We appreciate your patience during this transition and your continued input as R&D and engine teams refine these capabilities.

Kind Regards

Daniel