Risk warning: This forex platform incident log guide is educational information, not financial advice or investment advice. Leveraged forex and CFDs can cause substantial losses. A support record does not manage an open position, establish liability or guarantee compensation.
When a platform behaves unexpectedly, a clear description is more useful than a guess about the cause. This guide shows how to record what you observed, preserve its context and prepare a focused question for the firm’s verified support channel. It does not tell you to place, repeat, cancel or change an order.
If you need account-specific assistance, use the firm’s published contact route. Documentation should support that conversation, not delay it. Keep any decision about live exposure separate from this administrative checklist, and obtain appropriate professional advice when you need it.
Open a forex platform incident log with the observation
Write a short description of what you saw. A page did not load, a particular message appeared, or an expected confirmation was not visible. Avoid beginning with a conclusion such as the broker rejected my order unless the source you are recording actually states that.
Separate three things: what the screen displayed, what you were trying to do, and what you do not know. A clear note can say that a confirmation was not visible and the request’s status was uncertain. It should not assume an order failed, succeeded or disappeared simply because one view did not update.
Do not reproduce an account action to create a better screenshot. Keep the record of the event you actually observed. If you consult another screen or speak with support, add that later observation as a separate entry so it does not overwrite the first one.
Record the time and the environment you used
Note when you observed the issue and which clock you used. If the platform shows another time, keep it separately with its label. Do not silently treat local time, a device clock and a platform timestamp as identical.
Write down the application or browser you were using, the device type and the displayed version if you can obtain it without changing the account. Record whether the issue appeared in one view or several. These notes describe your experience; they do not diagnose a network, software or broker problem.
- What you observed and when you first noticed it.
- The name or location of the affected screen.
- The device and application context you can confirm.
- The wording of any visible message.
- The source of each timestamp.
- Any relevant status that remains unconfirmed.
If you remember a detail only later, label it as a later recollection. Do not give it the same status as a screenshot captured at the time. Honest gaps make the record easier to assess than precise-looking details reconstructed from memory.
Preserve originals before making a sharing copy
Keep the original screenshot or downloaded record unchanged. If you annotate a copy with arrows or a description, identify it as an annotated copy. Maintain a short index linking the file to the observation it supports, rather than renaming everything screenshot final.
Check each file after saving it. Is the relevant message readable? Does the image show enough surrounding context to identify the view? Did the export include the intended date range? Write down a limitation if the material does not show everything you hoped it would.
If your software offers a log or report, use its official documentation or support instructions to understand what the file contains. A technical log may require interpretation by the provider. This article does not provide commands, debugging changes or instructions to modify a live trading application.
Keep account secrets out of your forex platform incident log
Passwords, one-time codes and recovery information do not belong in a general incident timeline. Store sensitive original records appropriately and make a limited sharing copy when a verified recipient requests evidence. Do not post full account screenshots in public groups while looking for help.
Investor.gov’s alert on impersonation scams describes messages that use familiar organisations to seek sensitive information. Check a support contact independently rather than relying on an unexpected message offering to fix a problem. A request arriving during a stressful incident deserves the same scrutiny as any other request.
Before sharing a copy, review all visible panels, filenames and extra pages. Remove unrelated personal information from that copy while keeping the source original intact. Ask the recipient which secure route to use and what information is necessary. Do not send authentication codes as part of a ticket.
Build a timeline that separates actions and replies
Use one entry for each observation, contact attempt or response. State who supplied the information. Your description of a call, a message supplied by support and a platform notice are different sources even when they concern the same event.
An illustrative timeline might contain a screen observation, a later support enquiry, an acknowledgement and a subsequent update. It need not claim that the issue affected every customer or lasted continuously between two observations. Record the boundaries of what you know.
Keep reference numbers with their associated correspondence. If two teams or channels use different numbers, note the relationship only when it is confirmed. Avoid merging them into a single case based on a similar subject line.
Write a support request with one clear question
Open with the account context needed by the verified channel and a concise statement of the observed problem. Do not include credentials. Refer to the timeline and selected evidence, and state the particular status or process you want the firm to clarify.
For example, an illustrative request might ask the firm to confirm the status of a referenced request because the expected confirmation was not visible. It can also ask which official record should be used for reconciliation. It should not assert a technical cause, demand a promised payout or instruct another trade.
Before sending your own message, check that the attachments match its description and that the question can be understood without a lengthy narrative. Keep a copy of the submitted message and the channel used. If a form does not provide a receipt, record that limitation rather than inventing a case reference.
Check replies against the original question
Read the response beside your enquiry. Did it address the exact screen, period and account context? Did it explain the status you asked about, or provide a general troubleshooting page? Add a narrow follow-up when the answer does not resolve the uncertainty.
If a reply contains proposed account actions, do not treat this checklist as authority to carry them out. Confirm the contact route, understand the instruction and seek suitable advice for the situation. Preserve the message without turning it into an assumption that the underlying issue has been resolved.
For related background on checking a firm, see our broker-status guide. A familiar application or responsive support message does not itself establish that the contracting firm is authorised.
Know where this record-keeping routine ends
For background on forex risks, read the CFTC’s customer advisory. A neat record does not remove the risks of leveraged trading or make an account safe. Its purpose is to preserve a traceable account of what happened, including what remains unknown.
For UK consumer context, the FCA’s complaints guidance explains contacting the firm and recording the contact. Check the applicable procedure and eligibility for your own jurisdiction. This article does not determine whether an incident is a complaint, whether a deadline applies, or whether you have a claim.
Once the specific uncertainty is resolved, add a closing note describing the source of that resolution. Keep unresolved issues visible instead of marking the whole matter complete. Save the relevant final response with the original timeline so you can follow the record later.
Finish by checking whether another reader could follow the sequence without opening unrelated private files. The record should make clear what was observed first, which evidence supports it and who supplied each later answer. If the evidence does not settle a point, keep the uncertainty in plain language. A concise, accurate timeline is more useful than an elaborate account built on assumptions.
Risks to understand
- A screen observation may not establish an order’s actual status.
- Time labels, exports and logs can require clarification.
- A support record does not prove fault or guarantee a remedy.
- Impersonators may offer help while seeking private account information.
- Keeping notes is not a reason to delay account-specific assistance.
Further reading
- CFTC: Eight Things You Should Know Before Trading Forex.
- FCA: How to Complain.
- Investor.gov: Phishing, Smishing and Vishing Investor Alert.
A forex platform incident log should distinguish observations, source records and unanswered questions. Keep that distinction when you contact support. This is educational information, not financial advice or investment advice. Leveraged forex and CFDs can cause substantial losses; protections depend on your jurisdiction and contracting entity.