Skip to main content
This is the full list. Find your symptom, work through the steps in order — they’re ordered by how often each one turns out to be the cause, so stopping early is normal. Feature pages link here rather than repeat the steps, so these are the ones to follow. If nothing here matches, the last section tells you how to report it.

​
Signing in

1

Check which method your account uses

Two routes: Google, and a magic link — a one-time sign-in link emailed to you. There is no password field, because accounts made either way have no password. If you signed up with Google, use Google.
2

If the Google button isn't there at all

It is drawn by a script loaded from Google. An ad blocker, privacy extension, or network filter leaves an empty space and no error. Unblock the app’s domain and reload, or use the magic link, which doesn’t depend on Google.
3

If you see 'Too many login attempts'

Five failed attempts from one network in 15 minutes triggers a lockout. Wait 15 minutes, then use the magic link.
4

If it says your account is deactivated or scheduled for deletion

Both are deliberate states, not bugs. Email support@tradionlabs.com from the address on the account.
5

If you were signed in yesterday and now you're not

Sessions last 7 days and end without a warning. Sign in again. Clearing cookies for the app’s domain does the same thing, and is worth trying if the app is behaving strangely.
That screen appears when your browser window is narrower than 640 pixels. It is a width check, not a device check.
  • On a phone, expected. Sign-in works there; the terminal does not. Tap Email me a link for my desktop and open that link on a computer within 15 minutes.
  • On a tablet, rotate to landscape. Portrait on a small tablet can fall under 640 pixels.
  • On a desktop, widen the window, or press Ctrl/Cmd + 0 to reset zoom. A half-screen split or a heavily zoomed page is usually the cause. The screen clears itself once the window is wide enough.

​
Portfolio and brokerage

1

Allow pop-ups and relax tracking protection

The connection window comes from our brokerage aggregator, not from Tradion. Pop-up blockers and strict anti-tracking settings — Safari’s “Prevent cross-site tracking” especially — leave it blank. Allow both for the app’s domain and retry.
2

Finish the login on your broker's own page

You sign in to your broker, not to Tradion. Some brokers add a 2FA challenge — two-factor authentication, the code from your phone — and the window waits for it.
3

Approve read-only access explicitly

Close the window before approving the scope and no connection is created; nothing appears in Settings.
4

If the connection shows Expired

Brokers expire authorisations periodically, and always after a password change or 2FA reset. Settings → Connected Brokerages → Reconnect. Your imported history is preserved.
5

If your broker isn't in the list

Log trades by hand meanwhile — logging a trade — and tell us which broker at contact.
1

Sync manually

Nothing refreshes on a background timer. Click Sync Trades on the connection in Settings → Connected Brokerages, or Sync on the Portfolio page.
2

Wait if you synced a moment ago

Brokers rate-limit these calls. Syncing repeatedly inside a few minutes achieves nothing.
3

Check the account holds settled positions

A trade is settled once the cash and shares have changed hands, a day or two after you trade. Not every broker reports unsettled activity, so a fresh position can be invisible until then.
4

Check the connection status dot

An expired connection stops syncing silently apart from the status badge. Reconnect it.
5

If values differ from your broker's statement

Positions are valued on the last consolidated trade, which drifts from a broker’s mark outside regular hours, and multi-currency accounts convert at the aggregator’s rate. Both are covered in reading the dashboard. A persistent, material gap is worth reporting.
Working as built, not broken. Tradion writes one snapshot of your account value on each calendar day you open the Portfolio page, and the chart draws only those snapshots.
1

On day one, expect nothing

One point is not a line. There is no backfill of history from before you joined.
2

A gap means a stretch of days you didn't open the page

Nothing runs in the background to fill them in later, and syncing now will not recover them.
3

To get a continuous line, open Portfolio on the days you care about

That is the whole mechanism. See reading the dashboard.
Sector labels come from a fixed list of 16 mega-cap tickers. Everything else — small caps, ETFs, most of the S&P 500 — falls to Other. That is the lookup being thin, not your account being concentrated. Use the holdings table for the real picture.

​
Research

1

Give it the full time budget

A quant cell can run for up to 5 minutes, and can wait longer in the queue while the sandbox — the isolated cloud container your Python runs in — starts up. Two to three minutes of silence on a heavy analysis is normal.
2

Look for an error in the cell rather than a spinner

A step that genuinely fails shows a red error in the cell, not an endless spinner. If you see an error, jump to the next section.
3

If it's still spinning after roughly 12 minutes, reload the page

The live connection streaming progress to your browser can be cut by a proxy or a sleeping laptop, and the spinner has no way to know. Reloading recovers the session; completed work is saved.
4

Check your connection and any VPN

A VPN that drops long-lived connections is the most common cause of a spinner that never resolves.
5

Retry with a narrower question

Ten years of daily data across twenty tickers is a different job from one year across three.
Tradion already retries for you: a failing cell is re-run with a repaired version up to twice, then regenerated from scratch once. By the time you see a failure, four attempts have been made.
1

Read the error text at the bottom of the cell

A missing symbol, an empty date range, and a genuine code fault look completely different.
2

Check the asset is supported

US stocks and ETFs, crypto, forex, and US options. Futures, bonds, and non-US listings are not available — see supported assets.
3

Shorten the lookback and narrow the scope

Long histories over many symbols hit the 5-minute per-cell ceiling. Ask for less and the cell finishes.
4

Rephrase the question rather than editing the code

The generator responds better to a clearer question than to a patched prompt. Say what you want computed and what you want to see.
5

Start a fresh session if the whole canvas is failing

A new session spends a quant session from your monthly allowance. There is no way to re-run a single cell — see the canvas.
See the canvas for how cells work.
Lens takes a picture of your browser tab using a browser screen-capture feature, then reads the chart in it.
1

Use Chrome or Edge, on a desktop

Only those implement the capture path Lens uses. Safari and Firefox either hide the button or fail at the moment of capture. A button reading Desktop Only means your browser cannot do it.
2

Approve the share prompt and choose the current tab

Dismissing that prompt gives “Screenshot capture was cancelled or failed” — the same message every capture failure produces, so it is not always a permission problem.
3

Re-grant the permission if you blocked it once

Click the padlock or camera icon in the address bar, reset the screen-share permission for the site, and reload.
4

Make sure the chart is visible on screen

Lens captures what is displayed. A chart still loading, or scrolled out of view, gives a blank or unreadable frame.
5

If it says it can't read the ticker

Type the symbol into the box it offers and submit again. The screenshot is kept and re-analysed with the ticker you gave it.
6

Very large captures

A capture over 10 MB is rejected. Reduce your browser zoom or use a smaller window.
See Lens.
Price charts are drawn by an embedded third-party charting widget.
1

Turn off ad and script blockers for the app's domain

The cause the vast majority of the time. A blocked widget script leaves the chart area blank with no error, and Tradion has no way to detect it.
2

Check a network-level filter

A DNS blocker, corporate proxy, or filtering VPN can block the widget even with browser extensions off. Test on a different network.
3

If the chart loads but says the symbol is invalid

That message comes from the widget. Uncommon, over-the-counter, and non-US listings often will not resolve. Try the primary listing’s ticker.
4

If the price hasn't moved in a long time

Tradion shows no trading-halt banner, so a halted symbol looks like a normal static quote. Check your broker before acting on it.
5

Hard-reload the page

Ctrl/Cmd + Shift + R, to clear a half-loaded widget script.

​
Automations and alerts

1

Check it's switched on

Automations have an active toggle. Anything paused is skipped.
2

Check your subscription is current

When a subscription ends, every automation on the account is switched off. Resubscribing does not switch them back on — you do that yourself, one at a time.
3

Give it a full check cycle

Conditions are evaluated every 60 seconds. A trigger fires on the next check after the condition becomes true, not on the tick itself.
4

Check the condition is reachable

Compare the threshold with the live value. A level set the wrong side of the current price never becomes true.
5

Check the cooldown

The default is 60 minutes. A recent fire is deliberately suppressed until it expires.
6

Check the run history

Automations → Runs shows every evaluation and delivery attempt. An automation checking but never matching looks very different from one that never ran. See runs and history.
7

For scheduled automations, check the time zone

Schedules run in the automation’s own time zone, which defaults to US Eastern, not your local one.
Almost always one cause: the wrong kind of condition.
1

Check whether you chose 'goes above' or 'crosses above'

Goes above and goes below stay true on every 60-second check for as long as the condition holds. Crosses above and crosses below are true only on the check where the value moves through the level. For an alert you want once, use crosses.
2

Raise the cooldown

The cooldown is what stops a continuous condition repeating. Five minutes on a price level is a firehose; an hour is usually right.
3

Expect one extra fire the first time you save a crossing condition

With no previous reading stored, the first check falls back to a plain comparison. A condition already true when you save fires once immediately, then behaves as a crossing.
4

Narrow the symbol list

One automation watching twenty symbols is twenty chances to fire per cycle.
See operators and signal types.
You have hit your plan’s automation cap: 10 on Trader, 50 on Quant. Starter has none.The cap counts every automation you own, not the ones currently running. Pausing one does not free a slot — the only ways to make room are to delete an automation you no longer need, or to move up a plan. See plan comparison.
1

Open Automations → Runs and read the delivery status

Each run lists every channel it tried and the exact error returned. That separates “never fired” from “fired and failed to deliver”.
2

If the error mentions 404, the webhook was deleted

Deleting a Discord webhook, or the channel it posts to, breaks it permanently. This error is not retried and nothing switches the channel off for you — the automation keeps firing and keeps failing until you fix the address.
3

Create a fresh webhook and paste the new address in

In Discord: Channel Settings → Integrations → Webhooks → New Webhook → Copy Webhook URL. Paste it into the automation’s Discord channel settings.
4

Check the address is a real Discord one, over HTTPS

Only https:// addresses on Discord’s own domains are accepted. A shortened link or a proxy address is rejected before sending.
5

Check your server's permissions

A webhook posting into a since-restricted channel fails on Discord’s side, not ours.
6

Add a second channel as a backstop

Email or in-app alerts on the same automation mean a broken Discord webhook never costs you the alert. See notifications.
1

Check Settings → Monthly Usage first

It names which of the three meters is empty and when they reset.
2

Know what consumes each meter

A quant session is spent when you start a new analysis, not per question inside it. An agent run is spent per AI agent step per trigger — an automation with two agent steps costs two runs each time it fires. Chart analyses, Lens captures, earnings reports, autopsies, and portfolio syncs cost nothing.
3

Find the automation that's eating them

Agent runs are almost always the culprit, and almost always an agent on a high-frequency trigger. Automations → Runs shows which automation consumed what. Move the agent onto a daily or crossing trigger.
4

If agents stopped mid-month but your meter isn't empty

A separate short-term ceiling caps agent activity at roughly 20 runs an hour and 100 a day. When it is reached the automation still fires and still sends the alert; only the AI step is skipped. It clears on its own.
5

Note that failed agent runs are credited back

An agent that errors returns the run to your balance. A run spent on a successful-but-unhelpful answer is not refunded.
Full breakdown: usage limits.

​
Reporting something not listed here

Use the Feedback button in the left sidebar — it attaches your plan, page, browser, and a timestamp for you. Say what you expected, what happened instead, when, and which automation, analysis, or connection was involved. Full guidance on contact and feedback.

Contact and feedback

How to report a bug so it gets fixed quickly.

FAQ

Short answers to the questions we get most.