Codingame likes to give you test cases that don't include certain edge conditions while you're testing, and then throw those edge cases in during the actual validation. Chances are you ran afoul of one of them. Unfortunately, the test case data isn't available, so you'll need to examine your code and do some what-if work.
Try to think like an evil genius. If you were intentionally trying to make someone's code fail, what would you do? Can your code handle having Bender pass over the same spot from different directions without calling it a loop? With and without breaker mode activated? Before and after breakable blocks get destroyed? I don't know if any of that is actually necessary, but it is all possibly important. If your code is failing, you might want to take oddball stuff like that into account.
Other things to check: is there behavior in your code that allows some conditions to be incorrectly detected? A greater-than where you meant greater-than-or-equal? Is it possible that a null can slip in where it isn't expected and cause weird behavior?
If you catch me in chat and coded in something C-related, I'll be happy to have a look at what you have.