Release LoadGen Api, Appliance and MCP Server: 1.0.0.11930

LoadGen General

• No general changes in this release.

LoadGen Api

• [#8807] Fixed SessionSight Heatmaps still showing "Page snapshot unavailable" for sessions that did capture a page snapshot, even after the earlier heatmap background fix. The background lookup blindly took the first stored payload file for the session — which is almost always session-lifecycle data (clicks, pageviews) queued before the snapshot — rather than the file holding the page snapshot itself. The lookup now scans the session's earliest payload files (compressed ones included) and picks the one that actually contains a snapshot, so the page renders behind the heatmap again; sessions without any snapshot still degrade cleanly to the "preview unavailable" hint.
• [#8692] Added session-refresh support so the session-expiry warning can offer an Extend Session action that silently renews the signed-in user's session, replacing the confusing "Log in now" prompt (the user is still logged in at that point). Refreshes are only accepted in the final minutes before the token expires (default 5, tunable via the RefreshWindowMinutes security setting); earlier calls are rejected with a typed RefreshNotYetAllowed response so clients can back off and retry closer to expiry. Renewals are capped at 24 hours from the original sign-in even when chained (tunable via MaxSessionLifetimeHours), every refresh re-verifies the account still exists and hasn't been revoked, and each renewal is written to the security audit log. Sessions issued before this release simply start a fresh 24-hour window on their first refresh after upgrade.
• [#8843] Added PUT /appliance/influxdb/buckets/{bucketId}/retention so the retention policy of an existing InfluxDB bucket can be changed from within LoadGen — previously the datasource wizard warned "Only applied to buckets created for the first time" and the View Configuration modal showed every bucket's retention with no edit affordance, forcing operators into the raw InfluxDB UI or CLI. The new retention is supplied in seconds with 0 meaning infinite; negative values are rejected, unknown bucket ids return 404 with a typed BUCKETNOTFOUND code, and the endpoint responds 503 while the appliance agent is unreachable. This backs the new per-bucket edit-retention action in the appliance Services configuration view.
• [#8722] The Operations → LoadGen Tickets list can now show the developer's resolution comment on Resolved tickets (badge tooltip / expandable detail), so operators no longer have to wait for release notes or look the work item up manually to learn how a ticket was resolved. The API caches the most recently observed resolution text alongside the ticket's last-known status, letting the list render without a live lookup and keeping the text available in air-gapped environments. Older clients that don't send the new field keep working unchanged and never wipe previously cached text, and a stale status report can't overwrite a fresher snapshot — status and resolution are always updated (or dropped) together so a row never advertises contradictory state.
• [#8817] Fixed deleted uptime checks leaving their incidents stranded: an incident opened by a misconfigured check stayed Open forever after the operator deleted the check, with no underlying check left to navigate to. Deleting an uptime check — individually or via bulk delete — now automatically resolves any open incident for that check (resolution recorded as Auto, with end time and duration), broadcasts the resolution so subscribed clients refresh in real time, and cleans up the check's internal health-state tracking. Deleting a check that has no open incident behaves exactly as before.

LoadGen Appliance

• [#8843] The Appliance Agent now applies retention-policy updates to existing InfluxDB buckets, backing the API's new retention endpoint. The agent validates that the bucket exists before changing anything (unknown ids surface as a clean BUCKETNOTFOUND 404 instead of a generic gateway error), applies the new period — or infinite retention for 0 — through InfluxDB's admin API, and refuses InfluxDB system buckets (names starting with , such as monitoring and tasks) with a typed SYSTEMBUCKET_READONLY error.
• [#8840] Fixed the InfluxDB Setup step of the Services Configuration Wizard applying the Data Retention value in a different unit than operators expected: retention is now interpreted as days, in lock-step with the relabelled wizard fields (which previously said "hours"). Entering 30 now configures 30 days of retention — previously the value was applied as hours, so getting 30 days required entering 720. 0 still means infinite retention.

LoadGen MCP Server

• No MCP Server changes in this release.