Implement workflow completion monitoring with extensible hooks

[mvdbeek]

User facing changes

This PR adds the ability to configure actions that automatically execute when a workflow invocation completes. Users can now:

• Export results to a remote file source - Automatically export the invocation outputs to a configured file source (e.g., Dropbox, S3) when the workflow finishes

• Send a notification - Receive a notification when the workflow completes

• Inspect recent history and invocation exports

• Chose a history name when selecting "Send results to a new history"

The workflow run form includes a new "On Completion" section where users can select and configure these actions before launching a workflow.

Workflow Completion Monitor

The system uses a Celery-based polling mechanism to detect workflow completion:

1. WorkflowCompletionMonitor (lib/galaxy/workflow/completion_monitor.py) - A background task that periodically queries for invocations where all jobs have reached terminal states
2. WorkflowInvocationCompletion - A new database table that tracks completion status and prevents duplicate hook execution
3. Invocations gain a new completed state (distinct from scheduled) indicating all jobs finished

The monitor is limited to run only on the invocation handler to avoid contention in multi-process deployments.

Extensible Hook System

Hooks are registered in WorkflowCompletionHookRegistry (lib/galaxy/workflow/completion_hooks/init.py). Each hook extends WorkflowCompletionHook and implements:

• validate_config() - Validate user-provided configuration
• execute() - Perform the completion action

Built-in hooks:

• export_to_file_source - Exports invocation to a file source using the model store system
• send_notification - Sends a user notification via Galaxy's notification system

/api/exports Endpoint

New API endpoint for listing recent user exports:

• GET /api/exports?limit=50&days=30 - Returns recent exports to remote file sources
• Tracks both preparing (in-progress) and ready (completed) exports
• Used by the frontend to show export status in the Downloads panel

GCheckbox Component Refactoring

A new reusable GCheckbox component (client/src/components/BaseComponents/GCheckbox.vue) replaces BFormCheckbox usage in the workflow run form:

• Supports v-model with Vue 2.7-style value/input events
• Optional toggle prop renders a switch-style slider instead of a checkbox
• Includes data-test-id attributes for Selenium testing
• HelpText component gains an infoIcon prop for rendering help as an icon that doesn't interfere with click events

How to test the changes?

(Select all options that apply)

• I've included appropriate automated tests.
• This is a refactoring of components with existing test coverage.
• Instructions for manual testing are as follows:
  1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

• I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

[mvdbeek]

FAILED lib/galaxy_test/api/test_workflows.py::TestWorkflowsApi::test_run_workflow_subworkflow_conditional_step - AssertionError: Final state - completed - not okay.

😆 working too good

[mvdbeek]

Here's how that look like currently:

export_notification.mov

[jmchilton]

I mean the bottom right of this screenshot is kind of ugly - but I've opened many PRs with worse or no UI at all 😆. This isn't a blocker at all to me but I'm pointing it out if you want to clean it up. I'll review the backend again - give me a second.

[mvdbeek]

Alright, I think I addressed all of your comments (hope i didn't forget anything ...), and I updated the screenshots with the new state.