Reportworq 6 release notes#

What each Reportworq 6 release delivers for you. The latest hotfix is shown first, then each official release, newest first.

Release notes by version#

Each official release keeps its own page, authored once and left unchanged. The current hotfix is cumulative on top of the latest official release:

• Current hotfix - cumulative changes on top of 6.0.0.4.
• 6.0.0.4 - the latest official release.
• 6.0.0.3 - the previous official release.
• 6.0.0.2 - the initial Reportworq 6 release.

Latest hotfix#

The current hotfix build (6.0.1.13) contains every change below on top of the latest official release (6.0.0.4). Install the latest hotfix and you get all of it.

New#

• RW-2417 Native MCP clients and server-side agents can now sign in to Reportworq directly with your organization's own Microsoft Entra ID (or other OpenID Connect) identity provider. An administrator sets the public MCP server URL in Settings > Integrations > AI Agent Access; Reportworq then publishes it in its OAuth protected resource metadata (RFC 9728), so a client finds your identity provider, signs each user in and connects without an API key. See Direct OAuth sign-in for MCP clients.

Fixes#

• RW-2386 Platform A System Administrator can sign in to a load balancer node again (including with Microsoft Entra ID) to see its Activity, Status and Settings, and Settings > Load Balancer no longer shows an error once a node is registered.
• RW-2339 Distribution Running a Data Collection upload, with Run or Process All, now processes it instead of failing with "file is being used by another process" and leaving it stuck at Running.

Upgrade notes#

• Data Collection uploads that are already stuck at Running cannot be run again. Delete them and upload the files again after installing this hotfix.
• Direct sign-in for MCP clients stays off until an administrator sets the MCP server URL; until then, MCP sign-in works exactly as before.