Something looks broken
Give the support team a reproducible example with the page, scope, expected result, and observed behavior.
1 min read
A report is easiest to investigate when the team can reproduce one concrete example. Start with the page and what happened, then include the controls or source details that could change the result.
Write down the steps and the result
- Name the page, the action you took and the time it happened. Include the browser or device if layout or input behavior is involved.
- Describe what you expected and what appeared instead. Copy the visible error and any request or support reference shown by the app.
- Include the selected account, group, dates and time zone. For a trade, give its instrument and approximate execution time. For a cash movement, give the platform and transaction type.
- If you attach a screenshot or a source row, crop out unrelated account information and remove any credentials or personal data that the example does not need.
Include the source when it matters
For a sync problem, include the provider, connection status and last confirmed sync. For an import, include the file type, expected count, preview result and saved count. For a sign-in issue, include the sign-in method and the step that returned the error.
If the issue only happened once, report the one event you observed. Separate the exact message and time from your best guess at the cause.
Send the report to the team
Use Get help for an account or data problem. The support form keeps the details with your request so you can return to the conversation from Support settings. Use the bug report form for a reproducible workspace issue.
Did this article answer your question?