Phases & Execution Order (Bulk Panel)
The Bulk tab in the connector editor is where you enable/disable endpoints in bulk and arrange their execution order into phases and stages. It has three view modes — List, Flow, and Timeline — plus an AI reorder action and dependency-order validation.
Open it from the Bulk tab on the editor's left rail.
Concepts
- A phase is a top-level group that runs in order (phase 1, then phase 2, …).
- A stage is a group of endpoints inside a phase. Stages run in order within their phase.
- Endpoints inside a stage run together. Reordering respects dependencies: a source endpoint must run before any endpoint that consumes its output.
Phases/stages only exist once they have been created (typically via Reorder with AI). Until then the panel works as a flat enable/disable list and the Flow/Timeline views are disabled.
Toolbar
Common to all views:
| Control | What it does |
|---|---|
| Filter box | Filters endpoints by path, method, or category. |
| Counts | "N enabled · M disabled · T total". |
| View switcher | Three segmented buttons: List, Flow, Timeline. Flow and Timeline are disabled (greyed) until execution phases exist. |
| Reorder with AI | Sends the endpoints to AI to group them into phases/stages and order them by dependency. Disabled while a reorder is running or when there are no endpoints. |
Additional toolbar controls appear contextually:
- In List view, selecting endpoints reveals "N selected" plus Enable and Disable bulk-action buttons.
- In Flow view, Collapse all / Expand all and Add phase appear.
When an AI reorder finishes, the panel automatically switches to Flow view and expands everything.
List view
A flat, category-grouped checklist:
- A header row with a select-all checkbox and Method / Path / Enabled columns.
- Endpoints are grouped by category; each category header has its own checkbox (with an indeterminate state) and a collapse toggle, plus an enabled/total badge.
- Each endpoint row has a selection checkbox, a method badge, the path, and an enabled switch.
- Select any set of rows, then use the toolbar's Enable / Disable to toggle them together.
Flow view
The phase/stage editor (only available once phases exist):
- If there is more than one phase, a row of phase filter tabs (plus All) lets you focus a single phase. Each tab shows the phase name and endpoint count.
- Phases render as draggable sections; drag a phase by its handle to reorder it. Each phase header has an inline-editable name, an enabled/total count, a collapse toggle, and a delete (with confirm).
- Inside a phase, stages are draggable cards. Each stage card shows its global index range, an inline-editable name, an enabled/total count, a delete (with confirm), and a collapse toggle. Endpoint rows inside a stage show the global position, method badge, path, friendly name, and an enabled switch.
- Add stage (inside a phase) and Add phase (toolbar and a dashed button at the bottom) let you build structure manually.
- Renaming, reordering, adding, and deleting all flow through the editor's undo/redo and unpublished- changes tracking.
Timeline view
A read-only horizontal visualization (only available once phases exist): phases laid left-to-right with arrow connectors between them, each phase showing its stages and the endpoints (as coloured method dots with paths) inside. Use it to sanity-check the overall execution shape. If no phases exist it shows an empty state pointing you to Reorder with AI.
Reorder with AI
Clicking Reorder with AI streams an AI grouping pass. A loading overlay shows progress and the names being processed as they stream in. When it completes, the proposed phases are validated for dependency order before being applied (see below), and the panel switches to Flow view.
Dependency-order violations
If a proposed (or edited) order would run an endpoint before the endpoint that supplies one of its mapped parameters, a full-screen blocking modal appears. It has no close button — you must choose an option.
The modal lists each violation (deduplicated per source→target pair) with:
- A plain-language summary: which endpoint provides which JSON path as which parameter for which consumer, and how many positions too late it currently runs.
- A visual "Runs first (wrong) → Needed first" comparison with each endpoint's method, path, and its phase/stage location.
Two actions:
| Action | What it does |
|---|---|
| Fix automatically | Reorders the stages (topological sort) so dependencies are respected, then applies. |
| Fix manually | Dismisses the reorder and opens the Bulk edit so you can rearrange phases/stages yourself. |
Auto-fix only reorders to satisfy the dependencies it knows about. If the resulting grouping is not how you want it conceptually, use Fix manually and drag phases/stages into the shape you want — the validator will stop you again if you reintroduce a violation.
For the conceptual background, see Execution Order and Dependency Mapping.