Report a bug

Where the bug report form is on each surface, what each field means, and how to pick a severity that is neither inflated nor ignored.

Same on every platform Updated 26 July 2026

What this does

A bug report asks you for a structure: which part of the app, what kind of fault, how bad, and how to reproduce it. Filling those in gets your report looked at faster than the same information written as a paragraph.

Use this for something that is broken. Use Contact support for something about your account, your billing or your data.

Before you start

Have the reproduction steps clear in your head before you open the form. “It broke” produces a reply asking for steps. “Open Metrics, set the range to this year, press Save Layout, nothing happens” produces a fix.

If you can, take a screenshot before you leave the broken screen. The form accepts them and one screenshot usually replaces three messages.

Steps

Open Dashboard from the sidebar.
Press Report a Bug at the top right of the page. It opens the bug form in a new tab.
Fill in the fields described below.
Attach a screenshot if you have one, then submit.

Tap the circular avatar at the top right of Home to open Profile.
Tap Report Bug in the toolbar.
Fill in the fields described below.
Attach a screenshot if you have one, then submit.

Open the profile chip at the bottom of the sidebar.
Tap Report Bug in the toolbar.
Fill in the fields described below.
Attach a screenshot if you have one, then submit.

Tap the circular avatar at the top right of Home to open Profile.
Tap Report a Bug in the toolbar.
Fill in the fields described below.
Attach a screenshot if you have one, then submit.

Open the profile chip at the bottom of the sidebar.
Choose Report a Bug.
Fill in the fields described below.
Attach a screenshot if you have one, then submit.

The fields, and what to put in them

Title. One line. What broke, not how you feel about it.

App Area. Twelve options: Dashboard, Trading/Charts, AI Chat, AI Voice, Pattern Recognition, Journal, Portfolio, Communities, Account/Auth, Playbooks, Weekly Overview and Other. Pick the screen you were on when it happened, not the screen you think is at fault.

Bug Type. Seven options: UI/Visual, Functional, Performance, Crash, Data Issue, Feature Request and Other. Data Issue means a number is wrong. Functional means something did not do what it said it would.

Severity. Four levels, with the meaning we grade against:

Severity	What it means
`Critical`	App is unusable or data loss
`High`	Major feature broken
`Medium`	Feature partially works
`Low`	Minor issue or cosmetic

Grade it honestly. Everything marked critical is the same as nothing marked critical.

Detailed Description. What happened, in your own words.

Steps to Reproduce. Numbered. Start from a screen we can both open.

Expected Behavior and Actual Behavior. Two short lines. This pair is the most useful part of the whole form, because it tells us what you believed the product promised.

Screenshots. Optional and worth more than the rest combined for anything visual.

What you should see

A confirmation that the report was submitted. Reports are kept until they are resolved and for 90 days after that.

If it doesn’t work

The form will not open. It opens in a browser. Check that a pop-up blocker did not stop it.
You are not sure it is a bug. Check Start here: what’s actually wrong? first. Several things that look broken are documented behaviour.
It is about money, access or your data rather than a fault. See Contact support.

What to include in a support request The seven details that turn a support thread from four messages into one, and where to find each of them. Contact support The two ways to reach the VEXA team, which one to use for what, and what priority support on the Pro plan actually means. Start here: what's actually wrong? A list of symptoms with the article that fixes each one, so you do not have to guess which part of VEXA broke.

Still stuck? Email support@vexatrade.ai.