Activity

Activity helps you understand what happened inside the selected product and trading account. Use it with Positions and Orders to review automation behavior, broker sync events, trade events, and system messages.

1. Use the Trading Account Selector first

Before reading Activity, confirm the selected product, account mode, and account label. The Activity page should show events for the account you selected. Paper and live account activity are separate, and product lanes are separate.

2. Trade Activity

Trade Activity is focused on trading-related events. This can include buy events, sell events, close events, filled orders, trade updates, and other rows connected to automation actions. Use this section to see what the bot attempted or completed through the broker workflow.

3. What to look for in Trade Activity

• Symbol: the ticker connected to the event.
• Action: buy, sell, close, fill, or another supported trade event.
• Status: whether the event filled, opened, closed, skipped, failed, or needs review.
• Quantity and value: how much was involved when available.
• Realized P/L: closed-trade profit or loss when safely matched.
• Matched entry: the entry price connected to a close when available.
• Time: when the event was recorded or synced.
• Reason: safe explanation text when the system can show why something happened.

4. System Activity

System Activity is focused on account, runtime, sync, and readiness events. These rows are not always trades. A system sync can mean Bismel1 refreshed account state, updated broker data, checked runtime health, or recorded a non-trading account event.

5. What to look for in System Activity

• Broker sync: the app refreshed broker account, order, or position state.
• Runtime update: the automation cycle or product monitor updated status.
• Market data state: data was current, stale, unavailable, or not ready.
• Account readiness: broker or account setup needed attention.
• Skipped symbol: a symbol did not qualify or was not ready.
• System sync: an update happened, but it does not mean a trade was placed.

6. Difference between Trade Activity and System Activity

Trade Activity helps you review trade-related movement. System Activity helps you review app, broker, runtime, and data state. If you see a System Sync row, do not treat it as a buy or sell. If you see a trade row, compare it with Orders and Positions to confirm the broker-side result.

7. How to use Activity for automation monitoring

Start from the newest rows and work backward. Check whether the bot scanned symbols, whether any symbol skipped, whether any order was submitted, and whether the broker filled or rejected it. Then compare the Activity row with Orders and Positions for the same symbol and time.

8. Be patient with automation

Automation is a process, not a one-click promise. Some cycles may scan and do nothing because the setup is not ready. Some symbols may skip many times before a valid action appears. Give the app bot time to follow its checks, record activity, and avoid forcing trades when conditions are not ready.

9. Long-term review mindset

Use Activity to understand the pattern over time instead of reacting to one row. Review multiple days of events, skipped symbols, filled orders, closed trades, and system messages. Long-term success depends on disciplined monitoring, correct account setup, realistic risk control, and patience. Bismel1 does not guarantee profit or trading success.

10. When to pause or ask for help

If Activity shows repeated errors, stale data, broker readiness problems, rejected orders, or unexpected trade behavior, pause automation and review the account before continuing. When contacting support, include the product, account mode, symbol, time, page, and what you expected to happen. Do not send passwords, API keys, broker secrets, tax IDs, or bank credentials.