Query Pilot Script Orchestration
Help ID: query-runner.script-orchestration
Script orchestration lets one Query Pilot tab trigger a saved library script after the first script succeeds. It is for lightweight chains such as “deploy, then validate” or “run the main query, then run cleanup” without merging scripts into one large file.
Run After
In the Library pane, select a saved script and click Run after. The active tab records that selection and shows the follow-up label beside the library buttons. When the selected library script is already the active follow-up, the button is highlighted and changes to Run after on.
When the active tab runs successfully, Query Pilot opens the follow-up script in a new tab and runs it through the normal Query Pilot run path. The follow-up inherits the completed tab's pinned targets and selected databases.
Click the highlighted Run after on button again to remove that follow-up script from the active tab.
Recovery
Run-after settings are included in Query Pilot tab recovery autosave. If the GUI is restarted and the tab is restored, the follow-up script selection is restored with it.
Current Scope
This first version supports a simple success-only chain from the active tab to one saved library script. Future orchestration can add success/failure/always branches, prompts, and saved relationships between scripts.
Related: Query Pilot feature inventory, Tab autosave, Script library.
Documentation revision: E41BFB89427159BB