Activity
Search your server activity logs by date and command id to trace what happened to an action.
The Activity screen shows the server activity logs of everything AutoTrader Web did in your account. Open it from Tools -> Activity, pick an activity date, optionally enter a command id, and click Search. Use it to find out why an action (like a square-off or an order) did not work as you expected.
What the Activity screen is for
An activity is a trace, or log, of what the AutoTrader system is doing. It is a useful tool to investigate issues or problems in your account.
For example, you clicked Square-off but the square-off did not happen. You can open the Activity screen to find out what went wrong.
AutoTrader Web is a transparent system. You get full access to our server activity logs, so you can investigate issues yourself.
What is a command id
Every function in AutoTrader is treated as a command, and each command returns a command id to the caller.
You can use this command id to investigate one specific problem. For example, if one of your orders fails to reach the trading platform, you can filter the activity by its command id to see exactly what happened.
The command id is optional. If you leave it blank, you will see all activity in your AutoTrader account.
How to search activity
Go to the menu: Tools -> Activity. Then:
- Select Activity Date.
- Enter Command Id (if you have it, otherwise keep it blank).
- Click Search.
You will see the results in descending order of the time at which the activity took place.

Millisecond-level timing
Every activity entry is recorded with the time down to the millisecond.
This lets you measure exactly how long each step took. By comparing the timestamps of the steps in an activity, you can calculate, down to the millisecond:
- How long our system took to do an operation.
- How long your broker’s system took to respond.
This is useful when you want to check the speed of an operation, or find out where a delay happened.
Related pages
Next steps
Thanks for the feedback. Still stuck? Contact support.
Last updated 22 June 2026