Sync Evidence Console Manual
About This Manual
This manual explains how to use Sync Evidence Console to review local JSONL logs created by Sync Mushroom.
Sync Evidence Console organizes recorded events into readable views so that you can check command flow, execution timing, synchronization, close results, and related evidence without editing the original logs.
Sync Evidence Console does not place orders, change MT5, or automatically send log files anywhere.
The information shown in the console helps you identify where an issue or delay appears in the recorded workflow. It does not automatically determine the final cause or assign responsibility.
For a faster introduction, open the Quick Guide below.
1. Start the Console
- Open the Sync Evidence Console distribution folder.
- Start the included SEC launcher.
- Wait for Sync Evidence Console to open in your browser.
MT5 and Sync Mushroom Bridge do not need to be running when you review existing logs.
2. Load the JSONL Logs
Load the Sync Mushroom JSONL file for the time you want to review.
You can:
- Select the file, or
- Drag and drop it into Sync Evidence Console
When the activity spans several rotated log files, select all related files together.
After loading, confirm:
- The start time
- The end time
- The event count
Make sure the time of the issue is included.
3. Look at Dashboard First
Dashboard is the first screen to check.
It gives you a quick view of where recorded time appears in the workflow.
The main areas are:
- Panel / Local Bridge
Time before the command reaches the main local processing path.
- Sync Precheck
Local checks and preparation before MT5 execution.
- MT5 / Broker Execution
Time recorded between the MT5 request and response.
- Sync Catch-up
Local processing after the MT5 response.
- Panel Visual Sync
Time until the result appears in the interface.
The area with the largest or most elevated timing is usually the best place to investigate next.
This shows where the delay appears in the logs. It does not automatically prove the final cause.
4. Use This Simple Reading Guide
Panel / Local Bridge is elevated
Check:
- Whether the PC or browser was under heavy load
- Whether the command reached the local Bridge normally
- Commands
- Measured Evidence
This area covers the early local path before MT5 execution.
Sync Precheck is elevated
Check:
- Commands
- Measured Evidence
- Environment Boundaries
This area covers local checks and preparation before the MT5 request.
MT5 / Broker Execution is elevated
Check:
- Commands
- MT5 request and response
- Result code
- Reason
- Symbol and account context
This area is where the recorded MT5 request-to-response time appears.
Confirm the final result in MT5.
Sync Catch-up is elevated
Check:
- Commands
- Close Evidence, when reviewing a close
- Measured Evidence
- Raw Evidence
This area covers processing after MT5 has returned a response.
Panel Visual Sync is elevated
Check:
- Live Sync
- Measured Evidence
- Raw Evidence
This usually means the recorded result reached MT5 first and took longer to appear in the interface.
It does not mean MT5 execution took the same amount of time.
5. Check the Relevant Detail View
BUY or SELL issue
Open Commands and check:
- Action
- Symbol
- MT5 response
- Result code
- Reason
Position close issue
Open Close Evidence and check:
- Target position
- Result for that position
- Result code
- Reason
- Final recorded position count
Close All took time
Open Close Evidence and check:
- Number of target positions
- Result for each position
- Longest recorded close
- Failed count
- Retry information
Quote, profit, or screen update looked delayed
Open Live Sync and Measured Evidence.
Symbol, account, or terminal looks wrong
Open Environment Boundaries.
You need the exact event details
Open Raw Evidence.
6. What Common Results Mean
No data
The loaded logs do not contain the event type required by that view.
Unavailable or Insufficient data
The required events or timestamps are incomplete.
This does not automatically mean Sync Evidence Console is broken.
Partial
Only part of the related event chain is available in the selected log range.
Load the related rotated files if available.
Result code or reason is shown
Use it together with the events immediately before and after it.
Do not judge the full cause from one field alone.
7. Final Check in MT5
Sync Evidence Console reviews recorded logs.
It does not read the current MT5 state directly.
Use MT5 as the final source for:
- Current positions
- Current orders
- Trade history
- Account status
- Final execution result
8. Create a Submission Log Only When Needed
Use Download Submission Log only when you need to save a privacy-protected copy or support asks for it.
The file:
- Is generated locally
- Is not sent automatically
- Does not replace the original logs
- Protects selected account, financial, path, and ticket-related values
Review the generated file before sharing it.
9. Quick Review Flow
Load JSONL logs
↓
Confirm time range and event count
↓
Open Dashboard
↓
Find the timing area with the strongest signal
↓
Open the related detail view
↓
Check result code, reason, and related events
↓
Confirm the final result in MT5
Continue to 1. Product Overview for the full manual.
1-1 What Sync Evidence Console Is
Sync Evidence Console is a local log review interface for Sync Mushroom.
It reads JSONL log files already stored on your Windows PC and presents the recorded information through dedicated views.
You can use it to review:
- The time range covered by the loaded logs
- The number of recorded events
- The environment recorded in the logs
- Command flow from request to result
- MT5 request and response records
- Result codes and reasons
- Measured timing by processing stage
- Position-close and close-all results
- Quote, profit, and close-result synchronization
- Raw events and related event chains
- A privacy-protected Submission Log for support review
The available information depends on what was recorded in the loaded log files.
1-2 Relationship with Sync Mushroom
Sync Mushroom creates local JSONL logs while it is operating.
Sync Evidence Console reads those files afterward.
Sync Mushroom
↓
Creates local JSONL logs
↓
You load the logs into Sync Evidence Console
↓
The console organizes the recorded evidence
Sync Evidence Console does not send commands back to Sync Mushroom.
1-3 Local Processing
Loaded logs are processed locally in your browser.
Sync Evidence Console does not automatically upload the original logs or a generated Submission Log.
Nothing is shared unless you save a file and send it yourself.
2-1 Organizes Log Information
Raw JSONL files can contain many separate events.
Sync Evidence Console groups those events into views such as Dashboard, Commands, Close Evidence, Measured Evidence, and Raw Evidence.
2-3 Shows Measured Timing
The console can show timing for several parts of the recorded workflow, including:
- Panel / Local Bridge
- Sync Precheck
- MT5 / Broker Execution
- Sync Catch-up
- Panel Visual Sync
These values show where recorded time was spent.
A timing value alone does not prove the final cause of a problem.
2-4 Creates a Submission Log
You can generate a separately processed local Submission Log from the loaded data.
It applies designated privacy masking or transformation and necessary identifier aliasing. It is not an anonymity or cryptographic-encryption guarantee.
The file is saved locally. There is no automatic upload, email, or support-API submission; inspect it and share it manually only if acceptable.
Sync Evidence Console does not:
- Place BUY or SELL orders
- Create, modify, or cancel pending orders
- Change TP or SL
- Close positions
- Change MT5 settings
- Change account or terminal state
- Read the current MT5 state directly
- Automatically decide the root cause of an issue
- Automatically assign responsibility
- Automatically upload or send logs
- Replace the original JSONL logs
The final source for current orders, positions, history, and account status is MT5.
4-1 What You Need
To use Sync Evidence Console, you need:
- A Windows PC
- The installed Sync Evidence Console shortcut or included SEC launcher
- A supported web browser
- One or more Sync Mushroom JSONL log files
MT5 and Sync Mushroom Bridge do not need to be running when you review existing logs.
4-2 Starting the Console
- Start Sync Evidence Console from its separate Start Menu shortcut or the included SEC launcher.
- Wait for the local console to start and open in the selected browser.
- Load one or more JSONL log files.
SEC reads the JSONL files you select locally. MT5 and Sync Mushroom Bridge do not need to be running to review saved logs.
4-3 When the Browser Does Not Open
Keep the launcher open until the console is ready. If it still does not open, use the launcher’s displayed recovery information and see 20. Troubleshooting; do not guess a local address or port.
4-4 Closing the Console
When finished:
- Close the Sync Evidence Console browser tab.
- Close the SEC launcher window.
Closing only the browser tab may leave the local SEC server running.
5-1 Supported Format
Sync Evidence Console reads JSONL files.
A JSONL file stores one JSON event per line.
Typical file extension:
.jsonl
5-2 Finding the Logs
Sync Mushroom logs are stored locally on Windows.
A typical location is:
Documents / SyncMushroom / logs
The exact location can vary by product version or installation.
5-3 Rotated Log Files
A single activity period may be split across multiple log files.
When the issue or operation spans more than one file, select all related files together.
5-4 Keep the Original Logs
Loading a log does not modify it.
Generating a Submission Log also does not overwrite the original JSONL files.
Keep the original logs until the review is complete.
6-1 Select or Drop Files
From the initial screen, either:
- Select one or more JSONL files, or
- Drag and drop the files into the upload area
6-2 Loading Multiple Files
You can load multiple related files at the same time.
Sync Evidence Console combines the selected files and organizes the events by their recorded timestamps. It does not automatically deduplicate events, so select the related files deliberately and confirm the loaded range afterward.
6-3 Replacing the Current Session
Using Upload JSONL again replaces the currently loaded data.
It does not add a second set of logs to the existing session.
Select all required files together.
6-4 Parsing Status
Large files or a high event count may take longer to process.
Keep the browser tab open while parsing is in progress.
6-5 Invalid Lines
If a line cannot be read as valid JSON, the console skips that malformed line and shows a warning while continuing with valid lines. Parseable unknown events remain available in Raw Evidence.
The warning may include the file name, line number, and reason.
If no valid events can be loaded, the console shows an error.
6-6 Confirm the Loaded Range
After loading, first confirm:
- File name or number of selected files
- Start time
- End time
- Event count
Make sure the time of the activity you want to review is included.
The main navigation contains these views:
- Dashboard
- Evidence Matrix
- Live Sync
- Commands
- Close Evidence
- Measured Evidence
- Raw Evidence
- Submission
The top area also provides:
- Download Submission Log
- Upload JSONL
Changing views does not modify the loaded logs.
If a view shows No data, Unavailable, or Insufficient data, the required event type may not exist in the loaded range.
8-1 Start Here
Dashboard is the best place to begin.
It summarizes the loaded logs and shows the main recorded timing areas.
First confirm the loaded file range and event count.
8-2 Execution Summary
When enough command data exists, Dashboard shows an overview of the recorded workflow.
It may include:
- Overall condition
- Main observed signal
- Recorded timing
- Evidence source
- Confidence
- A link to the related detailed view
Use this summary to decide where to look next.
8-3 Reading the Timing Areas
The main timing areas are:
- Panel / Local Bridge
Time recorded before the command reaches the main local processing path.
- Sync Precheck
Time spent in local checks and preparation before MT5 execution.
- MT5 / Broker Execution
Time recorded between the MT5 request and response.
- Sync Catch-up
Time spent processing the result after the MT5 response.
- Panel Visual Sync
Time until the result is reflected in the user interface.
An elevated area shows where recorded time is concentrated. It does not by itself prove the final cause.
8-4 Statistics
Some sections show:
- Median
- p95
- Maximum
- Sample count
Review the sample count together with the timing values.
A single maximum value should not be used alone to judge overall behavior.
Median is the middle recorded value after the available observations are ordered. p95 is the level at or below which 95% of those recorded observations fall; compare it with Median to see whether a smaller tail of observations took longer. Maximum is the single largest recorded observation. Sample count is the number of observations included in that calculation.
Timing values that carry the ms label are milliseconds: 1,000 ms equals 1 second. Do not assume every value is a time; read the metric and its displayed unit. A low sample count makes Median, p95, and Maximum less representative, so load the relevant rotated logs where available and compare the related event chain before drawing a conclusion.
Confidence describes the available recorded basis for a displayed layer or measurement. It is not a probability that a cause is correct, and it does not prove responsibility, normality, or a final PASS/FAIL result. Treat Unavailable, Insufficient data, or a low-evidence indication as a reason to inspect related events or load more logs.
Environment Boundaries shows the environment recorded in the loaded logs.
Depending on the available data, it can include:
- Broker
- Server
- Account context
- Terminal context
- Symbol
- Route status
- Source files
- Financial values
Use this view to confirm that the logs belong to the account, terminal, symbol, and time period you intended to review.
Differences shown here are useful clues, but they do not automatically identify the cause of an issue.
Evidence Matrix separates the recorded workflow into major stages.
The standard stages are:
- Panel / Local Bridge
- Sync Precheck
- MT5 / Broker Execution
- Sync Catch-up
- Panel Visual Sync
Each stage can show:
- Recorded timing
- Availability
- Confidence
- Related evidence
- A link to a detailed view
Use Evidence Matrix when you want a stage-by-stage view of where time appears in the workflow.
- Start with the row for the stage where the symptom appears, then compare its Median, p95, sample count, availability, and Confidence with the other four rows.
- Open the row's related evidence or detailed view. For a command issue, continue to 12. Commands; for recorded timing, continue to 14. Measured Evidence; for display or quote reflection, continue to 11. Live Sync.
- Use the related-event path to compare the preceding request, the MT5 response when present, and the following result. If a row is Partial, Unavailable, or Insufficient, load related files if available instead of treating the missing record as proof of failure.
- The Matrix identifies where recorded time or missing evidence appears; it does not determine the final cause or replace final MT5 confirmation.
Live Sync shows recorded synchronization information.
Depending on the loaded data, it can include:
- Quote updates
- Bid and Ask values
- Profit updates
- Close-result notifications
- Position-count changes
- UI reflection
If Live Sync shows no data, the required synchronization events may not exist in the loaded files.
12-1 Command Review
Commands shows the recorded flow for actions such as:
- BUY
- SELL
- Pending order actions
- Modify
- Cancel
- Close position
- Close all
The exact action names depend on the loaded logs.
12-2 What to Check
For a command that did not behave as expected, check:
- Action
- Symbol
- Request
- MT5 request
- MT5 response
- Result
- Result code
- Reason
- Related event chain
- Recorded timing
12-4 Result Codes and Reasons
A result code or reason is one part of the recorded evidence.
Review it together with the events immediately before and after it.
- Choose the command whose Action, Symbol, and time match the operation you are investigating.
- Read the recorded Request, MT5 request, MT5 response, Result, Result code, and Reason in time order. A missing item means that item is not available in the loaded evidence; it is not proof that the operation did or did not happen.
- Follow the related-event path into 15. Raw Evidence when the summary does not explain the sequence, then return to the command chain to compare the recorded result.
- Confirm the final trade, order, or position state in MT5. If it is still unclear, retain the original logs and use 21. Before Contacting Support.
Close Evidence is designed for:
- Individual position close
- Close all
- Per-position results
- Failed close attempts
- Retry information
- Final recorded position count
A close-all operation may process multiple positions one at a time.
Review the result for each position rather than relying only on the total time.
If the chain is marked partial, some events may be outside the loaded log range.
The final confirmation source for closed positions is MT5.
- For an Individual Close, locate the target position and read its recorded request, MT5 response, result, result code, and reason.
- For ALL CLOSE, review each listed position separately. A completed result for one position does not establish the result for another position.
- If a result is failed or the chain is Partial, follow its related events and check whether the order was already changed, filled, or absent from the loaded range. Do not resend merely because the Console is incomplete.
- Verify every affected position in MT5; use the recorded evidence to guide the next check, not as a replacement for MT5 state.
Measured Evidence lists recorded measurements and state information.
Typical columns include:
- Layer
- Metric
- Source
- Value
- Timestamp
- Event type
Use filters to narrow the list by layer, source, metric, or event type.
Selecting an item may open its related event timeline or detail view.
- Begin with the layer or metric identified in Evidence Matrix or Commands, then filter by the matching symbol, action, event type, or time range when those controls are available.
- Sort or compare the displayed timestamp and value to locate the relevant observation, then select it to open its detail or related timeline.
- Check the metric name and unit before comparing values. If no matching measurement is present, treat it as missing evidence and continue with Raw Evidence or related log files.
15-1 Raw Evidence
Raw Evidence shows the loaded events in detailed form.
Use it when the summary views do not provide enough information.
15-2 Event Detail
Selecting an event can show:
- Type
- Source
- Metric
- Value
- Action
- Result
- Result code
- Reason
- Related identifier
- Full event object
15-3 Full Event Object
The Full Event Object contains the original event data available to the console.
Review the content before copying or sharing it.
Local account, financial, path, or ticket-related information may still be visible in the local review screen.
- Use filters or a related-event link to locate the event selected from Commands, Close Evidence, or Measured Evidence.
- Read the event timestamp, type, source, action, result, result code, reason, metric, and related identifier that are actually present.
- Move backward or forward through the related events to establish what was recorded before and after the selected event. If the chain ends or fields are absent, classify the evidence as incomplete rather than inventing a missing event.
Filters and sorting change only what is displayed.
They do not edit or delete the loaded logs.
Available controls vary by view and may include:
- Timestamp
- Action
- Result code
- Event type
- Layer
- Source
- Metric
- Latency
Use trace links to move from a summary to the related command, measurement, close evidence, or raw event.
17-1 A Command Feels Slow
Check in this order:
- Dashboard
- Evidence Matrix
- Commands
- Measured Evidence
- Raw Evidence
Identify which timing area contains most of the recorded delay.
Then open the matching Matrix row and related view, compare its sample count and Confidence, and inspect the linked command or raw events. A delay shown in one recorded area is an investigation lead, not a final cause; confirm the current trade state in MT5 before acting.
17-2 BUY or SELL Did Not Complete
Check:
- Action
- Symbol
- MT5 request
- MT5 response
- Result
- Result code
- Reason
- Related events
Confirm the final order state in MT5.
If the command is Partial, Unavailable, or missing a response, load the adjacent rotated logs if available and repeat the same command-to-raw-event trace. Preserve the original files for support if the chain remains incomplete.
17-3 A Position Did Not Close
Open Close Evidence and review:
- Target position
- MT5 response
- Result code
- Reason
- Final recorded status
- Related events
Confirm the final position state in MT5.
17-4 Close All Took Longer Than Expected
Review:
- Number of target positions
- Result for each position
- Longest recorded close
- Failed count
- Retry information
- Final recorded position count
17-5 Cancel or Modify Did Not Complete
Check:
- Action
- Order reference
- Symbol
- MT5 request
- MT5 response
- Result code
- Reason
The order may already have been filled, canceled, expired, or otherwise changed.
17-6 Quote, Profit, or UI Looked Delayed
Review:
- Live Sync
- Panel Visual Sync
- Measured Evidence
- Raw Evidence
UI reflection time and MT5 execution time are different measurements.
17-7 Symbol or Environment Looks Different
Review Environment Boundaries and confirm:
- Broker
- Server
- Account context
- Terminal context
- Symbol
- Route status
- Time range
18-1 When to Use It
Generate a Submission Log only when you need a separate processed local copy for further review or support asks for it. It does not provide cryptographic encryption, keys, or a decryption workflow.
18-2 Before Generating
Confirm:
- Correct files are loaded
- Correct time range is shown
- The relevant command or symptom is present
- You have reviewed Dashboard and the related detail view
18-3 Generating the File
Use Download Submission Log from the top area or the Submission view.
Wait for processing to complete.
The generated JSONL file is saved locally.
18-4 Automatic Sending
The Submission Log is not sent automatically by upload, email, or a support API.
Review the exported local JSONL. If remaining information is not acceptable, stop and retain it locally; otherwise you choose whether and how to share it manually.
18-5 Original Logs
Generating a Submission Log does not change or overwrite the original JSONL files.
19-1 Protected Information
The Submission Log applies masking or transformation to selected designated fields such as:
- Account and login identifiers
- Selected financial or account-related values
- Local file paths
- Comments
- Position, order, and deal references
19-2 Ticket Aliases
Position and order references may be replaced with aliases such as:
[TICKET_001]
[TICKET_002]
The same original reference uses the same alias within one generated file, allowing related events to remain traceable.
19-3 Information That May Remain
Information needed for technical review may remain. Masking does not guarantee anonymity or removal of every sensitive value, including:
- Timestamp
- Event type
- Action
- Symbol
- Lot or volume, price, SL, or TP
- Result code
- Reason
- Related event identifier
- Measured timing
- Broker or server context
- Source filenames, free-form or unknown fields, and device context
- Ticket alias
19-4 Review Before Sharing
Masking reduces unnecessary exposure, but you should still inspect the generated file before sharing it.
Check for:
- Account information
- Financial information
- Local paths
- License information
- Free-form text
- Any other information you do not want to share
20-1 The Console Does Not Open
Check:
- The SEC launcher is running
- No error is shown in the launcher window
- The launcher’s displayed recovery information is available; do not guess or manually substitute a local address or port
- A supported browser is being used
- Another SEC instance is not already using the same local service
20-2 No Logs Are Loaded
Use Upload JSONL or the initial file-selection area.
20-3 No Valid JSON Logs Found
Check that:
- The selected files are JSONL
- The files are not empty
- The files were not manually damaged or reformatted
- Each line contains valid JSON
20-4 Some Lines Were Skipped
Review the warning for the file name and line number.
Valid lines may still have loaded successfully.
20-5 Expected Data Is Missing
Confirm:
- The target time is within the loaded range
- All related rotated files were selected
- The selected logs came from the correct Sync Mushroom session
- The required event type was recorded
20-6 Large Logs Take Time
Large files can require more time for:
- Parsing
- Sorting
- Command-chain construction
- Evidence summaries
- Submission Log generation
Keep the browser open until processing completes.
20-7 Download Does Not Start
Check:
- Logs are loaded
- Processing has completed
- Browser downloads are allowed
- The destination has free space
Prepare the following information:
- Date and time of the issue
- Sync Mushroom version
- Sync Evidence Console version
- Action
- Symbol
- Result code
- Reason
- Related event identifier
- Final result shown in MT5
- Steps to reproduce
- Error message, if any
Before sharing screenshots, hide:
- Account number
- Account details
- Balance
- Equity
- Profit
- Local Windows user paths
- License information
- Other private information
Generate and share a Submission Log only when requested.
Sync Evidence Console shows only what exists in the loaded logs.
Results can be affected by:
- The selected time range
- Missing rotated files
- Missing or invalid lines
- Incomplete event chains
- Missing timestamps
- Product version differences
Sync Evidence Console helps you locate and review recorded evidence.
It does not replace MT5 as the final source for current trading status, and it does not automatically determine the final cause of an issue.