Troubleshooting

Only documented issues are listed — each with what is actually known (and its evidence) and a real next action. If your problem isn't here, that means it hasn't been verified, not that it isn't real: open a support request and include the guide or page you were on.

app.tradeflows.net does not load (error 522)

What is known: Observed directly: both .net origins answered 522 (origin unreachable) at the last recorded check (2026-09-17). A 522 means the server behind the address did not respond — a hosting-side state, not a problem with your device or browser. Separately, the audit could not confirm which build is deployed there (deployment status unverified).

What to do: Wait and retry later. Do not look for "the app" on other domains and do not enter credentials anywhere else. If it persists and you need the product, open a support request — say when you tried and what you saw.

The app shows a higher plan, but no payment ever happened

What is known: Documented source behavior: when the app’s billing endpoint is unreachable, the audited source falls back to a local-only mock that marks the plan as upgraded in your browser’s storage. That change is cosmetic — it is not a subscription, not a payment and not proof of one. The audit found no deployed billing route at all.

What to do: Treat the displayed plan as meaningless until billing is verifiably deployed. You were not charged — there is no working payment path in the audited source. If you did pay for TradeFlows anywhere, open a support request with the receipt details.

Charts or data areas are empty or stuck loading

What is known: The app reads market data through a separate read-only proxy service. The audit found two divergent copies of that service in the source and could not determine which (if either) is deployed — so a data outage is a plausible, documented failure mode.

What to do: Retry later. If it persists, open a support request and include which symbol/view you opened and the time. Do not reinstall or re-enter anything — there is no account to fix.

Something claiming to be TradeFlows asks for a password, API key or brokerage credentials

What is known: The audited app has no account system and no brokerage connection — identity in the source is a browser-local anonymous ID. No legitimate TradeFlows page needs those credentials.

What to do: Do not enter them. Report where you saw the request via the support page, and if you already entered credentials somewhere, change them at the real provider first. Security reports go to the restricted channel described on the support page.

Still stuck?

Contact support — include which issue above (or which guide step), the time, and what you saw. Saved requests can be checked any time on the status page.