Skip to content
Docs
Open Portal
Copy manually

Your browser did not allow direct clipboard access. Select and copy the text below.

PineConnector Edge

Change hosted EA settings, find broker symbols, and check signal routing, logs and connection details on PineConnector Edge.

Edge runs MT5 and the PineConnector EA for you. Manage it from your Mac or Windows browser; your computer can be off after setup.

New connection? Connect MT5, then test your setup before enabling your strategy.

Tab or area Use it to…
Experts See what the EA received and attempted.
Journal Inspect MT5 connections, order requests and broker responses.
EA Settings Change the hosted EA.
Symbols Find exact broker symbols and specifications.
Move to London Move an existing Virginia instance and check its version afterwards.
Update instance Review an offered update and verify the installed version.
Connection management Check recipients, Bridge processing, servers and instance controls.
Extra Edge terminals Add paid hosting within your existing connection allowance.

Edge supports MT5 with PineConnector, not MT4 or third-party EAs. Match your exact broker server with Portal’s live selector. For another EA or your own terminal controls, use self-hosted MT5 or a Windows VPS.

Edge and self-hosted connections share your plan’s connection allowance. Check access and available connections in Portal; legacy subscriptions can differ.

What you need Edge Your own Windows VPS
Who manages the environment? PineConnector runs MT5 and the PineConnector EA. You or your provider manage Windows, MT5 and the EA.
Where do you manage it? In Portal from your Mac or Windows browser. In the remote Windows desktop.
Which setup applies? MT5 with PineConnector on an available broker server. A supported Windows environment that permits the EA’s required DLL imports.
Where do you start? Follow Connect MT5 above. Connect to a Windows VPS, then install the MT5 EA.

If you need another EA or control of the Windows terminal, review the self-hosted path. Check its compatibility before installing. For Edge, Portal’s live broker-server selector is the final availability check.

On paid monthly Core, Plus and Pro, each extra hosted MT5 terminal costs US$35/month. Annual plans do not offer this add-on. Extra hosting uses your existing connections; buying a hosted terminal does not add a connection slot.

Plan Total trading connections Edge hosting included Maximum extra hosted terminals
Core 3 1 2
Plus 10 3 7
Pro 25 5 20

The included and extra hosted terminals together cannot exceed the total connection allowance. Edge-hosted and self-hosted connections share that same total.

For example, Plus with one extra terminal provides hosting for 4 of its 10 connections. It still has 10 connections in total, so up to 6 could be self-hosted while all 4 hosted connections are in use. This is an allowance example, not measured usage.

  1. Open Subscription in Portal. In Your plan → Extra Edge terminals, select Add terminals. You can also reach the purchase flow through Add Instance on the Edge page when more hosting is needed.
  2. In Add Edge terminals, choose the number of terminals to add. The dialog shows how many fit within your plan’s connection allowance.
  3. Review Today, the remaining billing period and the recurring total from your next renewal. The quote shows today’s prorated charge before you confirm; use your own displayed quote rather than a screenshot’s amount.
  4. Read the terms and recurring-charge authorisation, then confirm only if the quantity and price are correct. Complete bank approval if Portal requests it.
  5. Check the updated hosting allowance. Open Edge → Add Instance and follow Connect MT5 to set up the additional terminal.

Buying hosting and connecting a broker account are separate steps. Check the intended account, connection and demo setup result before relying on the new terminal.

  1. Open Subscription → Extra Edge terminals and select Remove.
  2. Set Terminals to remove and read the effective date and reduced recurring total.
  3. Review the effect on running terminals, then confirm only if the reduction is intended.
  4. Return to Subscription and check the pending removal and its date.

Removal takes effect at the next renewal, when the recurring charge decreases. It does not end the paid hosting immediately. Check that Subscription shows the pending reduction and its date.

Before that date, make sure your remaining hosted terminals fit within the reduced allowance. Review active alerts, positions and pending orders and arrange alternative hosting where needed. Losing hosting does not close broker positions. Contact Support if the removal screen does not make clear which running terminal will be affected.

See Subscription and billing before switching billing interval or cancelling the plan.

Experts shows what the PineConnector EA received and attempted. Open Portal → Edge, select your instance, then Experts.

Portal navigation, selected demo instance and Experts tab with date, Refresh and existing EA log entries
Experts in Portal, 6 October 2026. The sidebar, instance list and tabs show where to find the log.
Experts in Portal, 6 October 2026. The sidebar, instance list and tabs show where to find the log.Open original
Portal navigation, selected demo instance and Experts tab with date, Refresh and existing EA log entries

In either log tab, use the top-right date control (shown as Last 24 hours) to choose the date range. Select Refresh and check updated beside the entry count. Match time, symbol and order details across both tabs.

Close view: Experts log entries
Experts selected with date and Refresh controls, updated time and three existing demo log rows showing position counts, settings and a CLOSELONG signal
Close view of existing demo EA activity, 6 October 2026. This is a separate snapshot from the overview.
Close view of existing demo EA activity, 6 October 2026. This is a separate snapshot from the overview.Open original
Experts selected with date and Refresh controls, updated time and three existing demo log rows showing position counts, settings and a CLOSELONG signal

An attempt is not a completed trade. For an entry such as Attempt to Close Orders, match the Journal result and broker positions or history. Resolve an unclear outcome before sending the same trading command again.

Journal shows MT5 connections, order requests and broker responses. Open Edge → instance → Journal; use the same date and refresh controls. Check the intended broker account’s positions or history to confirm the trading outcome.

Portal navigation, selected demo instance and Journal tab with date, Refresh and recorded MT5 order messages
Journal in Portal, 6 October 2026. These are existing demo records, not a new test.
Journal in Portal, 6 October 2026. These are existing demo records, not a new test.Open original
Portal navigation, selected demo instance and Journal tab with date, Refresh and recorded MT5 order messages
Close view: Journal order result
Journal selected with date and Refresh controls and one complete demo order-result row for EURUSD
Close view of a demo order result, 6 October 2026. This is a separate snapshot from the overview.
Close view of a demo order result, 6 October 2026. This is a separate snapshot from the overview.Open original
Journal selected with date and Refresh controls and one complete demo order-result row for EURUSD

Portal filters routine MetaTrader update notices and internal service messages from these logs so the EA and terminal activity is easier to review. A filtered view is not the complete terminal service log.

The Experts and Journal screenshots show existing demo activity from different times, not one matched test.

Open Portal → Edge, select the intended instance, then EA Settings. Check its connection name and broker account: changes belong to this instance.

Portal with Edge selected in the sidebar, the demo instance selected, all four tabs and EA Settings open at General
EA Settings open at General for the selected instance, 6 October 2026. License IDs are hidden.
EA Settings open at General for the selected instance, 6 October 2026. License IDs are hidden.Open original
Portal with Edge selected in the sidebar, the demo instance selected, all four tabs and EA Settings open at General

Find the field under Syntax, Input, Maintenance, General, Account or Miscellaneous. Read its helper text and change only what you need. Pyramiding and Close on Reverse are under General. The unsaved count tracks draft edits; Discard resets them without saving.

Selected demo instance header, full tab row with EA Settings selected, settings status and General showing Pyramiding On and Close on Reverse Off
Selected instance panel, captured 6 October 2026: Pyramiding is On and Close on Reverse is Off. These demo values are not recommendations. More controls continue below.
Selected instance panel, captured 6 October 2026: Pyramiding is On and Close on Reverse is Off. These demo values are not recommendations. More controls continue below.Open original
Selected demo instance header, full tab row with EA Settings selected, settings status and General showing Pyramiding On and Close on Reverse Off

Check how your alerts use the settings:

Control Meaning
Input → Setting Chooses signal values or EA fields. With Signal Parameters Only, the EA’s Stop Loss, Take Profit and Risk fields are ignored; the alert supplies sl=, tp= and risk=.
Target Type How sl= and tp= are interpreted.
Volume Type How risk= is interpreted.
Broker Set Change only when Support asks you to.

See the EA settings reference for other controls and options, and Syntax for explicit-unit parameters.

Select Review & apply and check every previous and proposed value.

Review & apply showing Pyramiding from On to Off — Either 1 Buy OR 1 Sell, Close on Reverse from Off to On — Hedging, the approximately one-minute interruption warning, Cancel, and Apply and restart
Historical review example, 6 October 2026. The proposed changes were cancelled and discarded.
Historical review example, 6 October 2026. The proposed changes were cancelled and discarded.Open original
Review & apply showing Pyramiding from On to Off — Either 1 Buy OR 1 Sell, Close on Reverse from Off to On — Hedging, the approximately one-minute interruption warning, Cancel, and Apply and restart

Choose Cancel to revise the draft or clear it with Discard. When the values and interruption window are correct, select Apply and restart once.

3. Confirm application before relying on the change

Section titled “3. Confirm application before relying on the change”

Saved and applied are separate states. Read the settings status, not only the instance badge.

Status Meaning and next check
Saving… Save in progress. Wait for its result.
Saved — applies on next start Saved, but application is unconfirmed. Check settings status and terminal activity.
Applying your last change — the terminal is restarting. Restart in progress. Wait for it to finish.
Running Instance is running; this alone does not confirm the saved settings applied.
Historical instance header and complete tab row above Saved — applies on next start
Historical instance-panel view: Running does not confirm that saved settings have applied.
Historical instance-panel view: Running does not confirm that saved settings have applied.Open original
Historical instance header and complete tab row above Saved — applies on next start

During restart, Provisioning can appear and settings inputs and Send Test Signal are disabled.

Historical instance header, full tab row, Provisioning and Applying your last change — the terminal is restarting
Historical instance-panel view during a manual restart. The applying banner does not confirm active settings.
Historical instance-panel view during a manual restart. The applying banner does not confirm active settings.Open original
Historical instance header, full tab row, Provisioning and Applying your last change — the terminal is restarting

Reopen EA Settings. Check the values and that application is no longer pending; inspect startup and connection activity in Experts and Journal. Reading back saved values alone does not confirm the running EA uses them. Once confirmed, follow the demo verification steps.

Still pending, failed to save, or conflicting status? Contact Support with the time, status and affected setting. Avoid repeated restarts or signals; monitor positions and pending orders through your broker.

Use the selected account’s exact symbol and specifications. They can differ between account types on the same server.

Portal navigation, demo instance and Symbols tab with eurusd search, EURUSD result and specification panel
Symbols in Portal, 6 October 2026. Search is on the left; the selected symbol’s details are on the right.
Symbols in Portal, 6 October 2026. Search is on the left; the selected symbol’s details are on the right.Open original
Portal navigation, demo instance and Symbols tab with eurusd search, EURUSD result and specification panel
  1. Open Portal → Edge and select the intended instance.
  2. Open Symbols and enter EURUSD or your instrument in Search symbols. Search also matches descriptions; check the Symbol column.
  3. Select a row. Read Alert values for precision, contract size, volume limits and stops, and Identity for currency and path.
  4. Use the row or details-panel copy icon. Paste into your alert’s symbol field and verify the exact case, prefix and suffix, not the description.
  5. Check Updated. Use Check again to request an update, then recheck the timestamp and details.
Close views: EURUSD result and specifications
Focused Symbol and Description columns showing EURUSD, its copy icon and Euro vs US Dollar
Focused search result: eurusd returned EURUSD on Pepperstone-Demo, 6 October 2026. The exact symbol is separate from its description.
Focused search result: eurusd returned EURUSD on Pepperstone-Demo, 6 October 2026. The exact symbol is separate from its description.Open original
Focused Symbol and Description columns showing EURUSD, its copy icon and Euro vs US Dollar
Close view of EURUSD specifications: Digits 5, contract size 100,000, minimum and step 0.01 lots, and Stops level 0 points
EURUSD specifications on Pepperstone-Demo, 6 October 2026. Your own account’s current values can differ.
EURUSD specifications on Pepperstone-Demo, 6 October 2026. Your own account’s current values can differ.Open original
Close view of EURUSD specifications: Digits 5, contract size 100,000, minimum and step 0.01 lots, and Stops level 0 points

This Pepperstone-Demo snapshot reports the following for EURUSD:

Detail Example value Use it to check
Digits 5; point = 0.00001; pip = 0.0001 (10 points) Pip distances for the receiving symbol.
Minimal volume / Volume step Both 0.01 lots Minimum size and permitted increments, not a recommended trade size.
Stops level 0 points No reported minimum distance for sl= and tp=; other order requirements still apply.

These are reported specifications, not an executed trade. Full access and zero Stops level do not guarantee acceptance or a fill; check your symbol’s current session and order requirements.

Symbols says Waiting for the terminal

The initial symbol list has not arrived. Set up the same MT5 account on Edge again:

Historical instance header and full tab row with Symbols selected and Waiting for the terminal
Historical instance-panel view: the terminal has not yet reported its symbol list.
Historical instance-panel view: the terminal has not yet reported its symbol list.Open original
Historical instance header and full tab row with Symbols selected and Waiting for the terminal

Before terminating: review active alerts, open positions and pending orders, and choose a suitable interruption window. Termination does not close broker positions or cancel pending orders; keep managing them through your broker.

  1. Open Portal → Edge, select the affected instance, then Settings → Terminate instance.
  2. Choose Add Instance and follow the complete setup guide using the same MT5 account and broker server. Confirm the intended License ID and EA settings.
  3. After setup completes, open the new instance’s Symbols tab and check that the list appears.

Still waiting? Contact Support rather than repeatedly terminating and recreating the instance. Obtain the exact MT5 symbol and required specifications from your broker or Support; do not guess another account’s suffix.

Setup resolves the chart symbol after broker login; you do not enter it in the provisioning form. If setup fails, check the result and ask Support instead of repeatedly adding instances.

Alerts still require the exact case-sensitive broker symbol. Setup does not automatically map incoming TradingView symbols. For translation, check Symbol Mapping, including its plan requirements and configuration.

Open Portal → Edge and select the instance you want to move. Its card shows the current location, such as Virginia, US. Move instance switches between London and Virginia. The steps below show a move to London. For an instance already in London, check that its confirmation shows London, UK → Virginia, US instead.

Select Settings. The menu shows the installed Edge version and the Move instance action.

Portal Edge navigation, selected Virginia instance, full tab row and Settings menu showing Edge v3.49 and Move instance
Virginia starting state captured on 3 November 2026. Account details are redacted. The displayed version belongs to this example.
Virginia starting state captured on 3 November 2026. Account details are redacted. The displayed version belongs to this example.Open original
Portal Edge navigation, selected Virginia instance, full tab row and Settings menu showing Edge v3.49 and Move instance
Close view of Settings showing Edge v3.49, Restart instance, Move instance and Update instance
Detail from the same capture, with Move instance in the menu.
Detail from the same capture, with Move instance in the menu.Open original
Close view of Settings showing Edge v3.49, Restart instance, Move instance and Update instance

Select Move instance and check that the confirmation shows Virginia, US → London, UK for the intended instance.

The confirmation says the move uses your saved password, keeps the connection name and EA settings, and gives the rebuilt instance a new ID. Existing positions remain with your broker. Keep monitoring them there during the interruption.

Portal with Move instance confirmation showing Virginia US to London UK, the interruption warning, Cancel and Move instance
Move confirmation captured on 3 November 2026. This capture was cancelled before starting the move.
Move confirmation captured on 3 November 2026. This capture was cancelled before starting the move.Open original
Portal with Move instance confirmation showing Virginia US to London UK, the interruption warning, Cancel and Move instance
Close view of the move confirmation explaining the rebuild, preserved settings and interruption
Close view of the move confirmation: the rebuild, preserved settings and interruption.
Close view of the move confirmation: the rebuild, preserved settings and interruption.Open original
Close view of the move confirmation explaining the rebuild, preserved settings and interruption

Read the full confirmation. If the instance, destination or timing is unsuitable, select Cancel. When the details and interruption window are correct, select Move instance once.

Select Done when Portal confirms the instance is live in London. If the page still shows the previous location or Moving, refresh and select the instance again. Then check the instance shows London, UK and Running. Open Settings to read its Edge version. Check the installed version after moving. If Portal still offers Update instance, review that action separately after confirming the move has finished.

Portal Edge showing the moved instance Running in London UK with Settings open to its installed Edge version
After the move on 3 November 2026, the same demo account was Running in London. In this example, Settings still reported Edge v3.49 and offered an update.
After the move on 3 November 2026, the same demo account was Running in London. In this example, Settings still reported Edge v3.49 and offered an update.Open original
Portal Edge showing the moved instance Running in London UK with Settings open to its installed Edge version
Installed Edge v3.49 and Update instance still offered after moving to London
Installed Edge v3.49, with Update instance still offered after the move. This move retained the older Edge version.
Installed Edge v3.49, with Update instance still offered after the move. This move retained the older Edge version.Open original
Installed Edge v3.49 and Update instance still offered after moving to London

Check the intended broker account in Connections, then review EA Settings, Experts and Journal for the saved settings and fresh connection activity. A Running badge alone does not confirm signal delivery or a broker trade. Use the demo verification guide before relying on the changed setup.

If the move fails, the instance stays unavailable, or the displayed account or location is unexpected, contact Support with the time and visible result. Resolve the current state before attempting another move.

Use Update instance when Portal offers a newer Edge version. Open Portal → Edge, select the intended instance, then open Settings to read its installed version.

Choose Settings → Update instance. In the confirmation, check the instance name, the current and offered versions, and the position-management warning. In this example, the offered change was Edge v3.49 → v3.55.

Portal Edge in London with Update to the latest version confirmation and the interruption warning
Update confirmation on 3 November 2026, after the separate move to London. Account details are redacted.
Update confirmation on 3 November 2026, after the separate move to London. Account details are redacted.Open original
Portal Edge in London with Update to the latest version confirmation and the interruption warning
Update confirmation showing Edge v3.49 to v3.55 and warning that existing break-even and trailing-stop rules stop being managed
Close view of the version change and the position-management warning.
Close view of the version change and the position-management warning.Open original
Update confirmation showing Edge v3.49 to v3.55 and warning that existing break-even and trailing-stop rules stop being managed

The confirmation says the update uses your saved password, retains the connection name and EA settings, and gives the rebuilt instance a new ID. Choose Cancel if the interruption or position-management consequences are unsuitable. Otherwise select Update instance once.

Wait for Portal to confirm the update completed, then select Done. Check Running, the intended broker account and location, and the installed Edge version under Settings. Recheck EA Settings and fresh terminal connection activity. If the page still shows old information after the completion message, refresh and reselect the instance.

Portal Edge showing the London instance Running with Settings reporting Edge v3.55 and no Update instance action
The same London demo instance after the separate update on 3 November 2026. Settings now reports Edge v3.55.
The same London demo instance after the separate update on 3 November 2026. Settings now reports Edge v3.55.Open original
Portal Edge showing the London instance Running with Settings reporting Edge v3.55 and no Update instance action
Settings reports Edge v3.55 after the update
Installed Edge version after the update. Compare this with the version offered in the confirmation.
Installed Edge version after the update. Compare this with the version offered in the confirmation.Open original
Settings reports Edge v3.55 after the update

Running, a version label and saved settings do not prove that a signal executed or a broker trade completed.

The Edge instance version and the EA version are separate values. Open Connections → account → Terminal info to read both. Check the actual result before relying on the updated setup, using the demo verification guide where applicable.

If the update fails or the previous version is restored, read the result and check the current instance before taking another action. Contact Support with the time, versions and visible message if the outcome is unclear.

Check connection status after a network interruption

Section titled “Check connection status after a network interruption”

Portal updates the EA’s registration when it reconnects and ignores late disconnect messages from an older connection. Check the intended account in Connections, then match recent activity in Experts, Journal and Bridge. A connected label alone does not establish that a particular signal was processed or a broker trade completed.

If the EA appears disconnected despite current terminal activity, contact Support with the account context, event time and status. Avoid repeated restarts or trading commands while the outcome is unclear.

An alert’s License ID routes to every account connected to that ID, including shared Edge and self-hosted recipients. Check the assigned accounts in Connections before testing or enabling alerts.

Use a separate available ID for independent instructions. Do not disconnect a running account to free capacity without reviewing its automation. See the routing example or one alert, several accounts.

Open Portal → Bridge → Logs for signal-processing history. The Edge tag beside Signal ID distinguishes Edge processing from a self-hosted PC, laptop or VPS. Read Status for the processing result; check the intended broker account’s positions or history for the trading outcome.

Portal with Bridge selected, Logs and filters above existing demo rows showing Edge tags, In Progress and Success statuses
Bridge in Portal, 7 October 2026 (Singapore time). Existing demo activity includes In Progress and Success; processing status does not establish a broker fill.
Bridge in Portal, 7 October 2026 (Singapore time). Existing demo activity includes In Progress and Success; processing status does not establish a broker fill.Open original
Portal with Bridge selected, Logs and filters above existing demo rows showing Edge tags, In Progress and Success statuses
Historical close views: Edge tag and Status
Signal ID column with a redacted ID and blue Edge badge
Processing location
Status column with a green Success badge
Processing result

Two separate details from the same historical Bridge row, 18 September 2026. Processing success does not establish a broker fill.

Bridge history and test signals

Match the request’s time, account and result. Latency describes the recorded stage, not the whole TradingView-to-broker journey.

Historical Bridge heading, Logs tab, filters and two rows with timestamp, signal, account, action, latency and status columns
Historical Bridge view, 6 September 2026. Match the request you actually sent.
Historical Bridge view, 6 September 2026. Match the request you actually sent.Open original
Historical Bridge heading, Logs tab, filters and two rows with timestamp, signal, account, action, latency and status columns

PineConnector monitors the hosted terminal; continuous test signals are unnecessary. Use tests for setup or diagnosis. Send Test Signal on Edge is separate from the fixed connection-message check in the setup verification guide. Check the selected account and the confirmation before sending; a test that requests an order belongs on a demo account.

If Portal cannot confirm the Edge test within 15 seconds, it reports the uncertainty rather than leaving the control waiting indefinitely. An unconfirmed result does not mean the request failed. Check Experts, Journal, and the intended broker account’s positions and history before sending again, as a second send could duplicate a test trade. A late response remains associated with the instance that received the request.

A test is refused if the instance cannot act on it. A connection-message receipt does not prove a broker trade succeeded; use the separate demo-order verification.

Header field Meaning
Broker ping Terminal-to-broker measurement stored at last connect. Check Measured for its age. A dash means unavailable. It is neither live ping nor total alert-to-fill time.
Location Where the hosted instance runs. Useful connection context for Support, not trade confirmation.

Servers and Portal controls

Find a broker server

Registry updated 3 November 2026 from the supplied export, with 919 unique server entries. Portal’s live selector also reported 919 options. The 50 displayed names checked individually are marked Listed; other rows show Not checked. Match your exact server in Portal before connecting.

Date added shows when the server was added to the registry, not a guaranteed production activation date. Not recorded means the source has no date for that original entry.

Find an Edge MT5 server

For an FTMO account, check FTMO’s permitted strategies and automation rules for your actual account.

Continue with broker details in the setup guide.

Link to this answer
Where do I manage the connection after setup?
  • Connections → account: Recent signals, EA settings, Terminal info and Resources.
  • Bridge: processing history and test controls.
  • Edge → instance: Experts, Journal, EA Settings, Symbols and instance Settings.
Link to this answer
How do I view an account’s recent signals?

Open Connections → account → Recent signals. Match time, action and symbol; select View full log on Bridge for detail.

Historical Portal Connections navigation, account list and selected account with Recent signals and five demo rows
Historical Connections view with Recent signals selected; original identifier redactions retained.
Historical Connections view with Recent signals selected; original identifier redactions retained.Open original
Historical Portal Connections navigation, account list and selected account with Recent signals and five demo rows
Link to this answer
What does Terminal info show?

Connections → account → Terminal info shows the attached chart symbol, EA version, MT5 build and uptime to help identify the environment.

Historical Portal Connections navigation, account list and selected account with Terminal info
Historical Connections view with Terminal info selected. Use your connection’s current values.
Historical Connections view with Terminal info selected. Use your connection’s current values.Open original
Historical Portal Connections navigation, account list and selected account with Terminal info
Link to this answer
Where are the connection’s documentation links?

Open Connections → account → Resources for EA, syntax and setup guidance. The separate account controls below are not needed to read the docs.

Historical Portal Connections navigation, account list and Resources links above separate expanded account controls
Historical Connections view with Resources selected. Documentation links sit above the separate account controls.
Historical Connections view with Resources selected. Documentation links sit above the separate account controls.Open original
Historical Portal Connections navigation, account list and Resources links above separate expanded account controls
Link to this answer
Where do I restart or terminate an instance?

Open Edge → instance → Settings for Restart instance and Terminate instance. Review positions, pending orders and alerts first; keep monitoring the broker account while Edge is stopped.

Portal Edge navigation, selected demo instance and open Settings menu showing Restart instance and Terminate instance
Instance Settings in Portal, 6 October 2026. The menu is open; neither action was selected.
Instance Settings in Portal, 6 October 2026. The menu is open; neither action was selected.Open original
Portal Edge navigation, selected demo instance and open Settings menu showing Restart instance and Terminate instance
Close view: instance Settings menu
Settings menu showing Restart instance and Terminate instance
Close view of the instance menu, captured without selecting either action.
Close view of the instance menu, captured without selecting either action.Open original
Settings menu showing Restart instance and Terminate instance

Change broker is unavailable during restart. Wait for completion before changing accounts.

Link to this answer
Why is a view or expected activity missing?

Experts, Journal, EA Settings and Symbols are available. Confirm the instance, date range and refresh. A Symbols view waiting for the terminal has not received its list. Screenshots use a demo account. Contact Support if unresolved.

Link to this answer