Create and save Order Flow templates

Use templates for repeatable chart configuration

Order Flow templates are account-owned records that retain mode, appearance, overlays, burst criteria, lookback and candle interval. The picker sits beside Refresh data in the heading, and its selected record is the same one shown in Settings. A template is a configuration, not a captured-market archive. Selecting it does not bring back an old order book or copy one instrument's executions onto another. Name templates by their purpose, such as a compact footprint review or a quieter bubbles view, so the differences remain obvious during a busy session.

Create a fresh standard template

New uses built-in defaults rather than cloning the current draft. Choose it when you deliberately want to start from the standard configuration.

1. Open the template picker beside Refresh data.
2. Choose New at the bottom of the menu and wait for creation to succeed.
3. Confirm the newly created template is selected in the picker and Settings.
4. Adjust mode, lookback, interval, row grouping, overlays and appearance for the intended workflow.
5. Use the available naming and Save controls for that selected record, then check that the saved state matches the configuration you want to reuse.

Understand the starting defaults

A new time-chart template starts with Bubbles, a fifteen-minute lookback, one-minute candles, one native tick per price row and the standard appearance and signal defaults. It does not preserve the previous template's draft simply because the chart looked that way before you chose New. Creation selects the new record and returns the view to following live capture. While creation is pending, the prior selection and edits remain intact, and repeated New actions are blocked. If creation fails, inspect the message before trying again rather than assuming an unseen empty record was selected.

Save to the selected record deliberately

Header Save, modal Save actions, template naming and quick controls share one selected record and saved baseline. A visual change can make Save appear in the main heading. Saving updates that exact template rather than an unrelated default copy. If you continue editing while a save is pending, those later changes can remain dirty after the earlier save succeeds. Read the final state and save again only when you intend to persist the newer draft. A template selected from the menu should load its saved configuration before the first capture is treated as your chosen setup.

Switch templates without confusing local memory

The selected template identifier is remembered separately for the current account in the browser. The template settings themselves live on the account, so another browser can access the same records while beginning with a different selected template. Older default settings can remain a fallback when no remembered eligible template is selected. The picker focuses on time-chart templates; non-time footprint presets remain separate rather than being silently converted by a selection here. If an expected template is absent, verify its type and account before assuming it was deleted.

Recover from a revision conflict without losing intent

Concurrent saves use revision checks. A conflict retains your draft and offers Reload saved template inside Settings. Review your intended edits before using that action, because reloading intentionally replaces the local baseline with the current saved record. Repeated Save clicks with an outdated revision do not resolve which version you want. If several browsers edit one template, finish or record the preferred version before continuing elsewhere. A transient failure also deserves inspection: visible chart settings are local feedback until the server save confirms persistence.

Verify persistence and report the right evidence

To test a template, make a recognizable mode or appearance change, wait for a successful save, switch to another template and then select the saved one again. Confirm the same account, template name and active check mark. Test a reload in the same browser before comparing another browser's remembered selection. A restored configuration with unavailable data can still be a correctly saved template; source availability is a separate question. Include the template name, changed fields, last save state and whether Reload saved template was used when reporting a persistence or conflict issue.