The bot log shows your bot's automation activity. Bot logs are an efficient, helpful way to diagnose the actions your bots did or did not perform. Bot logs are useful because they provide insight into the decisions a bot has made and what errors it may have encountered.
A bot’s log is accessed in the Log tab of the bot dashboard.
The log is a record of all activity within a bot, including automations, events, errors, and manually opened and closed positions. The most recent activity is listed first, with the date and time the automation last ran displayed and the number of actions the automation performed.
You can filter to view certain types of automations or a combination of automations.
Selecting an automation from the log displays a detailed look at the automation’s decisions.
You can view decision recipes and all positions involved. For example, this position has nine actions because it had one decision criteria for eight different positions.
You can select any decision action block to view the selected field’s outputs when the automation ran. For example, this automation checked to see if the symbol price for all eight positions was below its 200-day SMA. SPY was $371.76 at 9:45, December 17th, which was not above the 200-day SMA of $317.76. Therefore, the automation ended.
Bot automations automatically run on a defined schedule. If you manually run an action, such as opening or closing a position, or use an immediate action like a button click, those are displayed immediately in the bot log and out of the sequence of your normally scheduled automations.
If an automation encounters an error, the action will be displayed in the bot log with a red circle and a brief explanation of why the bot discontinued the automation, such as exceeding capital and/or position limits.
Error messages are important because they help you identify and understand why an automaton could not complete an action based on the global safeguard settings you created.
You can select the automation with an error message to see when and why it stopped the decision-making process.