Release LoadGen Api, Appliance and MCP Server: 1.0.0.11847

LoadGen General

• Resolved cases where Swagger emitted empty schema references and where background workers could fail to start after upgrade.
• Added a startup diagnostic line so support bundles clearly show how configuration is being loaded after upgrade.

LoadGen Api

• [#8539] Fixed silent loss of users on load tests when the legacy profile-to-user data contained malformed or blank entries. Profile-to-user bindings are now trimmed and validated, malformed entries are skipped, and the "no users found" error includes a short breakdown so support can pinpoint the cause without inspecting the raw data.
• SQL Table-Naming Toggle Honoured Everywhere — the Create new tables per load test option now applies regardless of whether the SQL datasource uses the legacy or non-legacy connection mode, and the lookup follows the load profile's linked datasource instead of always picking the global active one. Toggling the flag in the dialog now reliably controls whether SMD/DUAF/PM tables get a timestamp suffix.
• Fixed a critical "SQL connection string is not configured! Cannot start test." error that aborted load tests when the load profile pointed at a legacy SQL datasource but the worker was configured for non-legacy mode. The connection string supplied by the API per test is now used whenever it is provided.
• Fixed a critical migration regression where Windows hosts with a Director configuration silently produced zero migrated load profiles. Director migration now reads the existing configuration again, so existing Director data (Users, Scenarios, Mail, Options, and Datasources) is visible after upgrade.
• Fixed the SQL datasource probe so legacy datasources without a stored connection string no longer report as Unreachable with internal jargon — they now return a clear "not applicable" status, while non-legacy datasources without a connection string return a plain "no connection string configured" message.
• Fixed 400 Bad Request errors when saving load profiles that included legacy or numeric values for agentAssignments[].agentType (such as 0, 1, 2, or normal/core/vdi). These are now normalized to the canonical Full/Core/Vdi values automatically.
• Fixed the runtime fallback for SQL sinks so a load test no longer fails to start with "SQL connection string is not configured" when the profile points at a headless-only datasource — the resolved datasource entry's pre-built connection string is now used as a fallback.
• Improved the Model validation failed log line to print a single readable string instead of System.String[], making API request validation problems easier to diagnose from logs.
• Improved the SQL sink startup error text with clear guidance for the operator on how to remediate.
• Restored an earlier change that had accidentally re-introduced the removed loadbots compound endpoint. User-facing agent management remains exclusively under the dedicated Full / Core / VDI agent endpoints; the removed compound endpoint is not coming back.
• Removed an orphaned permission entry for the long-removed loadbots compound endpoint.
• Wait Events and Performance Counter Settings catalogs — added new configuration endpoints for managing wait-event definitions and performance-counter settings, with corresponding Swagger tags.
• Load Profile Bundles — load profiles are now persisted as self-contained JSON bundles carrying schedule, user assignments, agent assignments, user-action assignments, scenario id, and typed Citrix/RDP/DUAF settings. Test schedules travel with the load profile they belong to.
• Improved migration logging for load-profile bundles so support bundles produced after a migration carry enough detail to triage migration issues directly.
• Migration of load-profile bundles now runs an additional repair/backfill pass so existing migrated bundles with missing user, agent, scenario, or protocol-specific fields are corrected on startup.

LoadGen Appliance

• Fixed potential start-up problems on Linux appliances after upgrade.

LoadGen MCP Server

• Wait Events and Performance Counter Settings tools — added MCP tools and sync entity types for wait-event definitions and performance-counter settings so they can be managed and synchronized via the MCP server alongside other configuration catalogs.
• Refreshed the documentation for the LoadBot tool to clarify that it operates only on the legacy compound view, and that user-facing agent automation now uses the per-type Full / Core / VDI agent tools.