Your cBot does not start or is missing from the list.
Automated trading is off, the cBot did not build, or it is in the wrong place.
cTrader gates automation the same way MetaTrader does, with more than one switch. There is a global automated trading control and a per-instance start, and a cBot that has been added but not started will sit in the list doing nothing at all. Because a cBot instance is bound to a specific symbol and timeframe, an instance can also be running perfectly while attached to something other than the chart you are watching, which looks like it is not working.
A cBot missing from the list altogether is a different problem. cTrader compiles cBots from source into runnable code, and a cBot that fails to build never becomes available to add, so it is absent rather than broken. Build errors are reported in the Automate area, which is why checking there is the first step when a cBot cannot be found at all.
A running instance shows as started and its log records activity as it evaluates. Check the instance is attached to the symbol and timeframe you intend, and watch the log through at least one bar close on that timeframe, since many cBots only act at bar close and silence before then is normal rather than a fault.
Check the global automation control after every restart, as with any platform that can place live orders automatically. Name cBot instances so you can tell which symbol each is running on. Test a new cBot on a demo account first and watch its log through several bars before letting it near live money.
Market Structure Pro gives one clear TRADE or NO-TRADE verdict on any MT5 chart, with confidence, grade and a plain-English reason. Free 7-day trial, no card.
Start free trial