Guide
Common problems
This section answers the most common operational questions: why a feature is blocked, why a notification did not arrive, why the sign-in process did not complete, and what to do when the interface shows a warning. Each entry names the exact state to check and the action to take.
What this section covers
- Why "Create" in the list manager shows a warning and the list is not created: the account is in demo mode. Demo mode blocks creating working lists. Complete sign-in via Telegram to get trial access, or restore the subscription.
- Why email sign-in does not finish after entering the password: new email accounts start in demo mode and require opening the confirmation link sent to that email before the account is fully active.
- Why the Telegram bind link does not work or shows as expired: the bind link is valid for 5 minutes only. If the time has passed, return to Account settings and generate a new link.
- Why Telegram is not available as a delivery channel option: the Telegram account is not yet bound to the user account. Go to Account settings and complete the Telegram bind flow first.
- Why Email is not available as a delivery channel option: the email address is either not set or not confirmed. Go to Account settings, enter the email, and open the confirmation link from the email that arrives.
- Why a price notification was not delivered to Telegram or email: check three things — is the delivery channel set? Is Telegram bound / email confirmed? Is the account subscription active? All three must be true.
- Why browser notification sound does not play when a notification fires: either the browser tab is muted, the device volume is zero, or the sound was not selected in Settings. Check the sound setting and tab mute state.
- Why the coin list loads slowly or shows a warning about data synchronization: more than 300 coins are enabled for one exchange/market pair. The warning is expected behavior and not an error — the data is loading, but it takes longer than for smaller lists.
- Why metric values look different after opening the product in a different browser: verify you are signed in with the same account. Settings are stored server-side and load automatically on sign-in.
- Why a server-side price notification moved to "Inactive" without firing: the subscription expired while the notification was active. Renew the subscription to reactivate it.
- Why the chart appears empty after switching coins — candles are not visible and the price area looks blank: the price axis scale was locked manually by dragging the axis. Double-click the price axis to restore auto-scaling.
Key screens and controls
- Demo warning dialog that appears when trying to create a list without an active subscription.
- Account settings showing email unconfirmed state with the "Send confirmation" button.
- Account settings showing the Telegram bind section in the "waiting for bind" polling state.
- Coin list showing the data sync warning banner for a large list.
- Browser notification permission state in account settings or browser settings.
Step-by-step flow
- If a feature is blocked with a demo warning: open Account settings, check the current access state (demo / trial / subscribed). If demo — complete Telegram sign-in or restore the subscription.
- If email confirmation was not received: check the spam folder. If nothing arrived, return to Account settings and resend the confirmation email.
- If the Telegram bind link expired: go to Account settings → Telegram bind section → generate a new link. Open it within 5 minutes.
- If Telegram is not receiving price notifications: verify that (1) Telegram is bound, (2) Telegram is selected as the delivery channel, (3) the subscription is active, and (4) the bot is not blocked in Telegram.
- If browser notifications are not firing: check that the browser granted permission (not "denied"), the tab is not muted, and the sound is configured in Settings.
- If the coin list shows the data sync warning: this is expected when 300+ coins are enabled. Wait for the initial sync. Consider reducing the coin count if the delay is too long.
- If settings appear missing after switching browsers: make sure you are signed in with the same account. Settings are stored server-side and load automatically on sign-in.
Screenshots
Screenshot placeholder
Demo warning when trying to create a working list
Show the exact warning that blocks list creation in demo mode and what action it points to.
Screenshot placeholder
Account settings — email not confirmed state
Show the unconfirmed email badge and the send confirmation button so users know the exact next step.
Screenshot placeholder
Data sync warning for a large list
Show the warning banner that appears when more than 300 coins are enabled, and explain it is expected.
Screenshot placeholder
Price notification in Inactive state after subscription expired
Show a previously active notification that moved to Inactive, and the path to reactivate it.
Operational notes
- Demo mode is not an error state. It is the default state for new email registrations and for users whose subscription has ended. The product is still usable in demo mode; specific features are limited.
- The Telegram bind link expires in 5 minutes by design. This is a security measure. Always generate a fresh link and use it immediately.
- Browser notification permission is managed by the browser, not the application. The application cannot override a "denied" permission — the user must go to browser settings manually.
- The data sync warning for large lists is informational. The data is loading; there is no action required unless the user wants to reduce the coin count.
- Server-side price notifications are not deleted when the subscription expires — they move to inactive. No data is lost.
- Settings are stored server-side in the user account. They follow the user across browsers and devices automatically after sign-in.
When to use it
- When something should already work but the visible behavior does not match what you expect.
- When you want to start diagnosing from concrete checks rather than general theory.
- When an alert fired but you got no notification, or a feature appears unavailable for no obvious reason.
When not to rely on it
- If you are still learning the product for the first time — start with the quick-start guide.
- If your question is only about a formula or where a specific control is located.
Typical interpretation mistakes
- Skipping explicit account, channel, and alert state checks and jumping straight to vague reassurances.
- Ignoring whether you are on a demo, trial, or paid plan when features seem locked.
- Assuming the UI appearance alone proves that backend delivery or verification is already complete.
Algorithms and formulas to understand
- Why demo mode blocks list creation but still allows the interface to load and be explored
- Why the 5-minute bind link expiry is enforced and what happens to a partially completed bind
- Why browser notification permission cannot be re-requested after denial and must be reset via browser settings