I see... In that case, if you see the word flashing on the terminal when run interactively, it seems clear what's happening: The code is printing the message then either backspacing over it, sending a 'clear line' command or similar, causing it to be erased from the screen. The logging/capture from the scheduler, on the other hand, is not a fully-featured interactive terminal, so it doesn't know how to do things like backspacing, clearing lines, etc., it just records what's printed, but never erases it.

No clue what module might be sending this, though. What modules do you use?