Leapwork Go 2026.15 brings significant refinements to timeline execution, including target-based track expansion and improved navigation from run results directly to source sequence steps. Additionally, the sequence header has been redesigned for better responsiveness and clearer control over recording, preview, and sequence locking states.
What’s new
HTTPS recording proxy
The recorder proxy now supports secure connections over HTTPS on port 8443, while the existing HTTP endpoint on port 8080 remains available temporarily to ensure a smooth transition.
Target-based timeline execution
Target-based tracks now continue executing until the configured target is reached, with the timeline graph automatically expanding to reflect the actual completion duration while preserving the configured final load. This ensures that performance tests accurately reflect real-world duration when targets take longer than initially estimated, providing teams with more predictable and transparent run results.
Direct step navigation from results
Users can now pinpoint specific steps for troubleshooting by using Ctrl/Cmd+click on a step title in the Timeline or Run Results to open that exact step in its source sequence. This is particularly useful for complex sequences where multiple steps share similar names or API headings, allowing for immediate inspection and editing of the logic behind a specific result.
What’s updated
Redesigned sequence header
The sequence header has been updated with a responsive design that clearly communicates recording, preview, and lock states, ensuring controls remain accessible across different screen resolutions and scaling levels. The new layout includes dedicated dropdowns for data items, AD users, and regions, while ensuring that long lock-owner names do not push critical controls off-screen.
Sequence lock synchronization
Sequence file locks are now synchronized in real-time using SignalR, ensuring that all users viewing a sequence are immediately notified of lock status changes or takeovers. This prevents accidental overwrites and provides a smoother collaborative experience by showing exactly who is currently editing, recording, or previewing a sequence.
Timeline ordering validation
New validation rules ensure that target-based sequences remain the final item on their track, preventing invalid ordering during add, edit, or drag-and-drop actions. This structural enforcement ensures that performance tests follow a logical flow where target-based goals are the concluding criteria for a successful run.
AI Chat SignalR normalization
The AI Chat panel now uses a normalized SignalR connection management system, improving the reliability of conversations and agent-based sequence creation during reconnection events. This technical refinement ensures that chat responses and automated sequence generation remain stable even if the underlying connection briefly drops or the authentication token expires.
Bugs and Improvements
This release includes the following fixes to improve stability and reliability:
-
Fixed an issue where API response values were stored in table data items even when the API call was skipped, preventing incorrect data propagation in subsequent steps.
-
Resolved a UI distortion issue on the canvas during preview runs with a large number of steps, ensuring the visual flow remains clear during execution.
-
Fixed a bug where the record button and blinking indicator were not syncing correctly across parallel browser sessions, providing a consistent view for all collaborators.
-
Resolved an issue where user details were not displayed correctly when navigating from Go to the Admin Portal, ensuring seamless profile management.
-
Fixed a bug where the last login details were not updating correctly for users with active, long-running sessions that spanned multiple days.
-
Resolved an issue where the AI Chat UI would remain in a loading state instead of showing an error message when the internet connection was lost.
-
Fixed a bug where imported file columns were appended to a table instead of replacing unsaved manual columns, maintaining the intended data structure.