BAD_SCHEDULE
What happened
A method scheduled with @fg.every or @fg.on is declared wrongly: it is a hook as well, it takes the wrong arguments, or the scheduling sits on a module-level function.
What to do
Schedule a method of the strategy class, give it the arguments (self, ctx), and do not schedule a hook.
Example
text
strategy.py, line 31: A scheduled method takes (self, ctx). [BAD_SCHEDULE]The wording of the message depends on your file, and the code does not. An error stops the file from loading.