Release LoadGen Api, Appliance and MCP Server: 1.0.0.11565

LoadGen General

• No general changes in this release.

LoadGen Api

• API Testing: Cross-Flow Invocation — flows can now call other standalone flows using the new flow.call node. Called flows run as nested executions with input/output variable mapping and circular reference detection.
• API Testing: Draft Revisions — flow graph changes are now auto-saved as mutable drafts without bumping the revision number. Commit explicitly when ready to promote a draft into a numbered immutable revision.
• API Testing: Single-Node Testing — test individual request nodes directly without running the full flow, with environment base URL and authentication profile resolution.
• API Testing: Run Execution Pipeline — queued flow runs are now dispatched and executed with real-time event streaming to connected clients. Runs progress through Queued, Running, and Completed/Failed states.
• API Testing: Revision Deletion — non-active flow revisions can now be deleted. Active revisions are protected from deletion.
• Workload Version Pinning — monitoring profiles and testing user bindings now support pinning a specific workload version. When set, test execution uses the versioned snapshot instead of the current file on disk.
• Workload Patch Versioning — added a patch option when uploading workloads to replace content at the current version without incrementing the version number.
• Per-Profile Datasource Selection — load profiles can now specify a dedicated datasource instead of using the global active one. Datasource validation ensures only compatible datasources are accepted.
• Datasource Category Filtering — the active datasource endpoint now supports category filtering, preventing monitoring datasources from appearing in the testing tab.
• Agent Validation on Profile Update — updating a load profile that has no agents mapped now returns a clear error instead of failing at runtime.
• Monitoring SQL Table Rotation — monitoring profiles now support configurable table rotation periods (monthly, half-yearly, yearly, or indefinite) for consolidated, time-partitioned SQL storage instead of creating a new table per session.
• External Login Scripts Management — new endpoints to download and upload custom Citrix external login scripts.
• Improved API documentation coverage — all endpoints are now fully documented with comprehensive Swagger metadata, request/response models, parameter descriptions, and error codes.
• Fixed an issue where the test-node endpoint ignored draft revisions and always loaded the committed version.
• Fixed workloads showing stale references to deleted load profiles, preventing workload deletion.
• Fixed a potential hang during shutdown when data ingestion workers were unresponsive.
• Fixed monitoring worker pool hanging on shutdown when a worker process failed to exit.
• Fixed incorrect SQL column name used for non-legacy datasource configurations.
• Fixed cloud monitoring packages not including image data from workload files.
• Fixed agent deserialization failures for cloud monitoring packages.
• Fixed Citrix PublishedApplication not being sent correctly when only the application ID was configured.
• Fixed run results not being immediately queryable after creation due to a file-system race condition.
• Fixed SignalR events not being received for API testing runs due to a timing issue.
• Fixed API diff summary showing inconsistent change counts.
• Fixed monitoring profile target environment configuration not being saved correctly, including missing Citrix and RDS connection fields.
• Fixed grace period behavior reverting to path-restricted mode for proper security during initial setup.
• Fixed root URL routing on the appliance returning raw API JSON instead of the frontend.
• Fixed target environment endpoints missing from the monitoring Swagger document.
• Fixed monitoring package technology defaulting to Citrix when no target environment configuration was linked.
• Fixed agent decrypting test user credentials incorrectly.
• Fixed RunAs profile resolution using the wrong data source for cloud monitoring agents.
• Fixed workload endpoints missing from the monitoring Swagger document.
• Simplified SQL datasource configuration — table type names are now derived automatically from the table prefix.

LoadGen Appliance

• Fixed root URL routing on the appliance returning raw API JSON instead of the frontend application.

LoadGen MCP Server

• Added datasourceName parameter to load profile creation and update tools.