Error codes
Every TraceX error code (TX-1xxx to TX-5xxx), what it means, and how to fix it. The dashboard links each error message to its section here.
When something can’t be done, TraceX shows a message you can act on, followed by a TX code, for example Your plan’s limit is reached. Upgrade on Billing. (TX-3002). In the dashboard, click How to fix next to the message to jump straight to that code below.
For errors on TraceX’s side (TX-5xxx) it also shows a reference: send it to support and we can find exactly what happened. TraceX never shows raw database or system errors; they are logged under the reference.
How to read a code
Section titled “How to read a code”| Range | Means | Usually |
|---|---|---|
| TX-1xxx | Sign-in and permissions | Sign in again, or ask an admin for access. |
| TX-2xxx | Something about the request | Check what you entered. |
| TX-3xxx | Plans, limits and seats | An admin can upgrade or assign a seat. |
| TX-4xxx | A connected system | Check the integration’s credentials or permissions. |
| TX-5xxx | Something on TraceX’s side | Try again; if it persists, send the reference to support. |
TX-1xxx: Sign-in and permissions
Section titled “TX-1xxx: Sign-in and permissions”| Code | HTTP | Message |
|---|---|---|
TX-1001 |
401 | Sign in to continue. |
TX-1002 |
401 | Your session ended. Sign in again. |
TX-1003 |
403 | You don’t have access to this. |
TX-1004 |
403 | Set up two-factor sign-in to continue. |
TX-1005 |
401 | That email and password don’t match. |
TX-1006 |
423 | This account is locked for a few minutes. |
TX-1001
Section titled “TX-1001”Sign in to continue. · HTTP 401
What it means: You aren’t signed in, or the dashboard couldn’t find your session.
How to fix it: Sign in again at app.tracexpro.com. If it keeps happening, allow cookies for app.tracexpro.com.
TX-1002
Section titled “TX-1002”Your session ended. Sign in again. · HTTP 401
What it means: Sessions end after a while, when you sign out elsewhere, when your password changes, or when someone revokes the session under Profile → Sessions.
How to fix it: Sign in again. For the CLI, run tracex login. For an AI tool, create a new token.
TX-1003
Section titled “TX-1003”You don’t have access to this. · HTTP 403
What it means: Your role doesn’t allow this action, or the project is restricted to other members.
How to fix it: Ask an admin to change your role or add you to the project.
TX-1004
Section titled “TX-1004”Set up two-factor sign-in to continue. · HTTP 403
What it means: Your organization requires two-factor sign-in and you haven’t set it up yet.
How to fix it: Follow the prompt, or open Profile → Two-factor sign-in. See Two-factor sign-in.
TX-1005
Section titled “TX-1005”That email and password don’t match. · HTTP 401
What it means: The email or password is wrong, or the account signs in with Google or single sign-on instead.
How to fix it: Check the email, try Forgot password, or use the sign-in button your organization uses.
TX-1006
Section titled “TX-1006”This account is locked for a few minutes. · HTTP 423
What it means: Too many failed sign-in attempts, so sign-in is paused to protect the account.
How to fix it: Wait a few minutes and try again, or reset your password.
TX-2xxx: The request
Section titled “TX-2xxx: The request”| Code | HTTP | Message |
|---|---|---|
TX-2001 |
422 | Some of the details aren’t valid. |
TX-2002 |
400 | That request couldn’t be completed. |
TX-2004 |
404 | We couldn’t find that. It may have been removed. |
TX-2005 |
405 | That action isn’t available here. |
TX-2009 |
409 | That already exists. |
TX-2010 |
409 | That changed in the meantime. Reload and try again. |
TX-2013 |
413 | That is too large to upload. |
TX-2015 |
415 | That file type isn’t supported. |
TX-2029 |
429 | Too many requests. Wait a moment and try again. |
TX-2001
Section titled “TX-2001”Some of the details aren’t valid. · HTTP 422
What it means: A field is missing or in the wrong format.
How to fix it: Check the highlighted fields. For integrations, compare your values with the example on the integration’s docs page.
TX-2002
Section titled “TX-2002”That request couldn’t be completed. · HTTP 400
What it means: The request didn’t make sense in the current state, for example acting on something that’s already finished.
How to fix it: Reload the page and try again.
TX-2004
Section titled “TX-2004”We couldn’t find that. It may have been removed. · HTTP 404
What it means: The item was deleted, belongs to another project or organization, or the link is wrong.
How to fix it: Go back and open it from the list. Check you’re in the right project.
TX-2005
Section titled “TX-2005”That action isn’t available here. · HTTP 405
What it means: The action can’t be used on this item.
How to fix it: Reload the page; if the button is still there, contact support.
TX-2009
Section titled “TX-2009”That already exists. · HTTP 409
What it means: Something with the same name or address is already there, such as a member invite or a connection.
How to fix it: Use the existing one, or pick a different name.
TX-2010
Section titled “TX-2010”That changed in the meantime. Reload and try again. · HTTP 409
What it means: Someone else changed the same thing while you were editing.
How to fix it: Reload to see the latest version, then make your change again.
TX-2013
Section titled “TX-2013”That is too large to upload. · HTTP 413
What it means: The file is over the upload size limit.
How to fix it: Split the document, or upload a smaller export (for example Markdown instead of PDF). See Knowledge base.
TX-2015
Section titled “TX-2015”That file type isn’t supported. · HTTP 415
What it means: TraceX can’t read this kind of file.
How to fix it: Upload Markdown, text, reStructuredText, HTML, PDF or Word (.docx). See Knowledge base.
TX-2029
Section titled “TX-2029”Too many requests. Wait a moment and try again. · HTTP 429
What it means: Too many requests in a short time, from you or your organization.
How to fix it: Wait a minute and try again. Plans also limit AI requests a minute; see Plans.
TX-3xxx: Plans, seats and billing
Section titled “TX-3xxx: Plans, seats and billing”| Code | HTTP | Message |
|---|---|---|
TX-3001 |
402 | Your plan doesn’t include this. Upgrade on Billing. |
TX-3002 |
402 | Your plan’s limit is reached. Upgrade on Billing. |
TX-3003 |
402 | You don’t have a seat in this organization. |
TX-3004 |
429 | Your plan’s usage for this period is used up. |
TX-3005 |
402 | This is older than your plan’s history. |
TX-3010 |
403 | Paid plans are not available yet. |
TX-3011 |
502 | The payment provider couldn’t complete that. Try again. |
TX-3001
Section titled “TX-3001”Your plan doesn’t include this. Upgrade on Billing. · HTTP 402
What it means: This feature is part of a higher plan.
How to fix it: Compare Plans; an admin can upgrade on Billing.
TX-3002
Section titled “TX-3002”Your plan’s limit is reached. Upgrade on Billing. · HTTP 402
What it means: You’ve reached a limit such as projects, sources or monthly investigations.
How to fix it: Check usage under Settings → Plan and limits. Remove something you don’t use, or ask an admin to upgrade.
TX-3003
Section titled “TX-3003”You don’t have a seat in this organization. · HTTP 402
What it means: The organization has more members than seats, and you’re one of the members without one. You can still view everything.
How to fix it: Ask an admin to give you a seat or add seats on Billing. See Seats.
TX-3004
Section titled “TX-3004”Your plan’s usage for this period is used up. · HTTP 429
What it means: The organization used its AI allowance. AI work pauses for a cooldown, then resumes.
How to fix it: Wait for the cooldown, or ask an admin to upgrade. See What the limits mean.
TX-3005
Section titled “TX-3005”This is older than your plan’s history. · HTTP 402
What it means: The item is older than your plan’s report history.
How to fix it: Upgrade for longer history. See Plans.
TX-3010
Section titled “TX-3010”Paid plans are not available yet. · HTTP 403
What it means: TraceX is in private beta and paid plans aren’t open yet.
How to fix it: Nothing to fix. Contact hello@tracexpro.com if you need more than your beta access.
TX-3011
Section titled “TX-3011”The payment provider couldn’t complete that. Try again. · HTTP 502
What it means: The payment provider returned an error.
How to fix it: Try again in a minute. If a payment is involved, check Billing before retrying so you don’t pay twice. See Subscribe and pay.
TX-4xxx: Connected services
Section titled “TX-4xxx: Connected services”| Code | HTTP | Message |
|---|---|---|
TX-4001 |
502 | We couldn’t reach that service. Try again. |
TX-4002 |
400 | That service didn’t accept these credentials. Check them and try again. |
TX-4003 |
503 | This isn’t set up on TraceX yet. |
TX-4004 |
502 | That service returned an error. Try again. |
TX-4005 |
503 | The AI model is busy or unavailable. Try again in a minute. |
TX-4001
Section titled “TX-4001”We couldn’t reach that service. Try again. · HTTP 502
What it means: TraceX couldn’t connect to the system: it’s down, the address is wrong, or it only accepts connections from known addresses.
How to fix it: Check the address and that the system is reachable from the internet. Databases in a private network need network access; contact support. See Troubleshooting.
TX-4002
Section titled “TX-4002”That service didn’t accept these credentials. Check them and try again. · HTTP 400
What it means: The key, token or password is wrong, expired, or lacks a permission TraceX needs.
How to fix it: Create a new key with the permissions listed on the integration’s page and connect again.
TX-4003
Section titled “TX-4003”This isn’t set up on TraceX yet. · HTTP 503
What it means: The feature needs configuration on TraceX’s side that isn’t done yet.
How to fix it: Contact hello@tracexpro.com.
TX-4004
Section titled “TX-4004”That service returned an error. Try again. · HTTP 502
What it means: The connected system answered with an error.
How to fix it: Try again. If it persists, check the system’s status page and the credentials on Integrations.
TX-4005
Section titled “TX-4005”The AI model is busy or unavailable. Try again in a minute. · HTTP 503
What it means: The AI provider is overloaded or briefly down.
How to fix it: Wait a minute and try again. Your request wasn’t counted twice.
TX-5xxx: TraceX itself
Section titled “TX-5xxx: TraceX itself”| Code | HTTP | Message |
|---|---|---|
TX-5000 |
500 | Something went wrong on our side. Try again. |
TX-5001 |
503 | TraceX is having trouble saving data right now. Try again in a minute. |
TX-5003 |
504 | That took too long. Try again. |
TX-5004 |
503 | TraceX is briefly unavailable. Try again in a minute. |
TX-5000
Section titled “TX-5000”Something went wrong on our side. Try again. · HTTP 500
What it means: An unexpected error in TraceX. It’s logged under the reference shown with the message.
How to fix it: Try again. If it keeps happening, send the reference to hello@tracexpro.com.
TX-5001
Section titled “TX-5001”TraceX is having trouble saving data right now. Try again in a minute. · HTTP 503
What it means: TraceX’s storage is briefly unavailable.
How to fix it: Wait a minute and try again.
TX-5003
Section titled “TX-5003”That took too long. Try again. · HTTP 504
What it means: The request timed out.
How to fix it: Try again. For questions, narrow the time range or be more specific.
TX-5004
Section titled “TX-5004”TraceX is briefly unavailable. Try again in a minute. · HTTP 503
What it means: TraceX is restarting or under maintenance.
How to fix it: Wait a minute and try again.
Investigation ids
Section titled “Investigation ids”Investigations have ids like TX48211794554145: TX, four random digits, and the
time the investigation started. They aren’t error codes; quote them to support when a
question is about one investigation.
Still stuck
Section titled “Still stuck”Email hello@tracexpro.com with the code, the reference and what you were doing. See also Troubleshooting.