Error messages explained

What this does

VEXA does not invent error text. Every message you can see comes from one shared list that is compiled into the web app, the iOS app and the Android app, so the same fault reads the same way wherever you hit it. The table below is generated from that list at build time, which means it cannot drift from what the apps actually say.

How to read a VEXA error

Every message has three parts, and they always appear in the same order.

1. The title. A short line such as “Connection trouble”. This is the category.
2. The body. One sentence saying what happened.
3. The action. One sentence saying what to do. If there is nothing useful to do, the app says so rather than inventing a step.

Some surfaces also print a code such as resource-exhausted or auth/too-many-requests. If you can see a code, search for it in the table below. If you cannot, search for the title.

Every message

Code	What you see	What it means	What to do
auth/invalid-credential	Couldn't sign in	That email or password didn't match our records.	Try again or use Forgot Password to reset.
auth/user-not-found	No account found	We couldn't find an account with that email.	Check the email or create a new account.
auth/wrong-password	Couldn't sign in	That email or password didn't match our records.	Try again or use Forgot Password to reset.
auth/email-already-in-use	Email already in use	An account with this email already exists.	Sign in instead, or use a different email.
auth/weak-password	Password too weak	Please choose a stronger password.	Use at least 8 characters with a mix of letters and numbers.
auth/invalid-email	Invalid email	Please enter a valid email address.	No action needed.
auth/too-many-requests	Too many attempts	We've paused sign-in for a few minutes for your security.	Wait a moment and try again.
auth/network-request-failed	Connection trouble	We couldn't reach our servers.	Check your internet and try again.
permission-denied	Access denied	You don't have permission to do that.	Try signing out and back in. If it keeps happening, contact support.
unavailable	Connection trouble	We're having trouble reaching our servers.	Check your internet and try again.
deadline-exceeded	That took too long	The request timed out before we could finish.	Please try again.
resource-exhausted	You've hit a limit	You've reached the limit for this feature on your current plan.	Wait for your next reset or upgrade your plan.
file-too-large	File too large	That file is bigger than we can process.	Try a smaller file or split it into parts.
broker-disconnected	Broker disconnected	We've lost the connection to your broker.	Reconnect from your profile.
subscription-required	Pro feature	This feature is available on the Pro plan.	Upgrade to unlock it.
already-subscribed	Already subscribed	You already have an active VEXA subscription.	Manage or change your plan from your profile instead of starting a new checkout.
schedule-unavailable	Plan change not scheduled	We couldn't schedule this plan change, and no charge was made.	Please try again shortly or contact support.
default	Something went wrong	We hit an unexpected snag.	Please try again. If it keeps happening, contact support.

Steps

What you should see

After the action in the table, the box disappears and the screen you were on loads normally. Errors in this list are transient by design: they describe a condition, not a broken account.

Four that get misread most often

• “You’ve hit a limit” is about your plan’s monthly allowance, not a fault. See What happens when you hit a limit.
• “Pro feature” means the screen exists and your plan does not include it yet. See Why a feature is locked.
• “Broker disconnected” means your broker stopped accepting VEXA’s read-only credential. Your imported trades are untouched. Reconnect from your profile.
• “Something went wrong” is the fallback for anything with no specific message. It is the one case where telling support what you were doing at the time genuinely changes the answer.

If it doesn’t work

• The message on screen is not in the table. Some screens print text from the service they were talking to rather than from VEXA’s own list. Copy it exactly and send it to support.
• The same message returns every time. See Contact support, and include the code.
• You are not sure which subsystem is failing. Go back to Start here: what’s actually wrong? and route by symptom instead.