Release LoadGen Api, Appliance and MCP Server: 1.0.0.12121

LoadGen General

• No general changes in this release.

LoadGen Api

• Reliable API startup. Fixed an issue that could stop the API from starting — a misconfigured exception-handler pipeline caused the API container to crash-loop before it began serving requests. The API now starts reliably and returns standard problem-details JSON (RFC 7807) for otherwise-unhandled errors. Requires an API redeploy.

LoadGen Appliance

• Safer appliance self-update. Hardened the appliance's built-in self-update so an agent update can no longer install a build that does not actually run, or disrupt the rest of the stack while updating. Updates now stage and swap atomically, and the new agent must pass a health check before the update is committed — rolling back automatically if it fails (any HTTP response counts as proof of life, so an agent whose health endpoint requires authentication is not wrongly rolled back). An agent-only update no longer restarts the whole stack, so it cannot take the API, frontend or HTTPS down. This also closes a race where a background watchdog could relaunch the previous version mid-update (causing an update to silently not take), and a rare case where a stale proxy configuration left HTTPS failing with ERRSSLUNRECOGNIZEDNAMEALERT until a manual reload. Requires an Appliance Agent redeploy.

LoadGen Core Agent Appliance

• No Core Agent Appliance changes in this release.

LoadGen MCP Server

• No MCP Server changes in this release.