FAQ
Last updated
Last updated
If you're unable to open positions through the notification buttons after connecting your Bybit or OKX account via API keys in Tree Terminal, here are some common causes and solutions:
API Connection Issues:
Cause: Tree Terminal may be unable to fetch your account balance or other account information.
Solution: Restart Tree Terminal after adding your account. This often helps sync the API connection properly.
Anti-Misclick Setting:
Cause: The "anti-misclick" feature prevents trades if the mouse doesn’t move a few pixels before clicking to avoid accidental clicks.
Solution: Disable the "anti-misclick" setting in Tree Terminal’s settings and try again.
Bybit Unified Trading Account (UTA):
Cause: Bybit’s Unified Trading Account may require specific configuration for API functionality to work.
Solution: Check and adjust your UTA settings as outlined in Bybit’s documentation: .
OKX's Margin Setting:
Cause: OKX requires specific configuration for API functionality to work with Tree Terminal
Solution: Ensure that you have configured multi currency margin mode + cross + one way
API Restrictions:
Cause: Restrictions or errors specific to your API setup may prevent functionality.
Solution: Ensure your account is properly configured, and all required API permissions are granted, such as enable-futures.
Verify that your API keys are correctly entered and have the necessary permissions for trading and account balance access.
Test the feature on another device or network to rule out local issues.
If the issue persists, gather any error messages and contact Tree Terminal support with details about your setup.
If you're not receiving tweet notifications from a specific account in Tree Terminal, despite having them enabled, it could be due to the "Filtered" setting.
Cause: The "Filtered" option is turned on for the account. When this setting is enabled, only tweets matching specific filters (e.g., keywords) will trigger notifications.
Solution: Check the "Filtered" column for the account in your settings. If the "Filtered" option is enabled, you can:
Disable "Filtered" to receive all tweets from the account.
Adjust the filters to match tweets you want to be notified about.
Open the settings in Tree Terminal for the account in question.
Look for the "Filtered" toggle in the account's row.
If "Filtered" is enabled:
Disable it if you want to receive all tweets.
Or review and update the filter criteria to ensure relevant tweets match.
If "Filtered" is off and you're still not receiving notifications, check:
The "Notification" toggle to ensure notifications are enabled.
Your overall notification settings for Tree Terminal and your device.
If notifications are not appearing as expected, it’s possible that Focus Mode on the News Feed has been enabled by accident. Focus Mode limits updates to specific feeds or settings, which can block notifications.
Check if the toggle icon (highlighted in the red box) on the News Feed component is switched on.
If Focus Mode is enabled, click the toggle to disable it and resume receiving all notifications.
If notifications are still not coming through after disabling Focus Mode:
Verify that your notification sources are active under Settings > Notifications.
Test the feeds using the "Test It!" button to ensure they are configured correctly.
Disabling Focus Mode should resolve the issue and restore real-time notifications to your terminal.
Yes, Tree Terminal’s custom TWAP feature is not limited to 10 TWAPs, as it computes the limit order locally and sends it directly to ByBit. Unlike ByBit’s native TWAP system, Tree Terminal’s implementation does not rely on ByBit starting or managing the TWAP.
Custom TWAPs in Tree Terminal:
Tree Terminal computes and manages the TWAP locally, allowing you to run more than 10 TWAPs simultaneously.
ByBit Throttling:
While unlikely, ByBit might throttle requests if too many orders are sent in rapid succession.
Solution: If throttling occurs, space out the start times of your TWAPs slightly to avoid triggering ByBit’s rate limits.
Best Practices:
Always set a maximum size limit for your TWAPs, such as max_250k or max_1m, to ensure controlled execution.
Monitor your TWAPs periodically to ensure they are executing as intended.
How do I split orders across multiple accounts?
If you have multiple accounts and want to distribute the order equally across them, tick both options in settings > account: ✅ Buy On All Accounts ✅ Split the amount to buy across all accounts simultaneously
Example:
You place a 100k long order.
If you have 4 subaccounts, each will receive 25k of the total order.
If you want to maximize margin usage on each account before moving to the next, only tick the first box: ✅ Buy On All Accounts ❌ Split the amount to buy across all accounts simultaneously
Example:
You place a 10M BTC long order.
First account has 10x leverage and 500k balance, so it will long 5M.
If more size is needed, it will move to the next subaccount, and so on.
What happens if neither option is ticked?
The system will only execute the order on the first account and ignore other accounts.
Example: A 10M BTC long will only fill on the first subaccount (if margin allows) and will not continue to the others.
By selecting the right option based on your strategy, you can control how orders are distributed across your accounts efficiently.
To remove unwanted notifications, follow these simple steps:
Manually Dismiss Notifications:
Right-click directly on the notification you want to remove.
Use Keyboard Shortcuts:
Navigate to Settings → Shortcuts.
In the search bar, type "Close All Notifications".
Assign your preferred shortcut (e.g., Shift + Backspace) to quickly clear all notifications at once.
Optional shortcut settings:
Close Last Notification: Quickly clear only the most recent notification.
Close Oldest Notification: Remove the oldest notification from the list.
Choose the method that best suits your workflow.
It can be confusing to find your subscriptions through the mobile app settings. In the app, under the section "Account & Device", the entry "Pushover dashboard" does not show your subscriptions. Instead, it provides options such as resetting your email, password, enabling quiet hours, and "do not disturb".
To see all your subscriptions:
Scroll down to view all devices and subscriptions linked to your account.
Confirm your subscription:
Adjust Alert Settings in Mobile App:
Open the Pushover app, navigate to Settings → Alert Settings.
Enable "Play high-priority as alarm" to ensure notifications marked with high priority (+1) make a sound even if your phone is silent or in "Do Not Disturb" mode.
Android-specific settings:
Enable "Allow background usage" for the Pushover app to prevent delays or missed notifications.
Use the provided tool to send test messages to your devices.
Experiment with different priority levels, especially priority +1, to verify if notifications trigger correctly and produce sound alerts in silent or "Do Not Disturb" modes.
Follow these steps to ensure seamless use and management of your Pushover notifications.
Log into your Pushover account through a web browser at .
Upon logging in, you'll be redirected to , your actual dashboard.
Log in at and verify your subscriptions.
Log into your dashboard at .
