# Bug with a for Loop **URL:** \ **Category:** General Questions\ **Tags:** configuration, migrated\_question\ **Created:** [November 4, 2024, 8:14am UTC](https://community.exalate.com/t/bug-with-a-for-loop/5580 "2024-11-04T08:14:26Z")\ **Posts on this page:** 2\ **Page:** 1

**Author:** ![xl8bot](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/xl8bot/32/324_2.png) [@xl8bot](https://community.exalate.com/u/xl8bot)\ **Post date:** [November 4, 2024, 8:14am UTC](https://community.exalate.com/t/bug-with-a-for-loop/5580/1 "2024-11-04T08:14:26Z")

_Originally asked by Harold Oconitrillo on 14 September 2023 [(original question)](https://oldcommunity.exalate.com/questions/88246557)_ * * * When you put a “\<” character in the for condition, the code does not detect it when opening and closing the braces. I attach a screenshot where you can see the word “for” in grey. When I put \<= if it detects the keys correctly, I attach the screenshot where you can see how the for is set to blue and the keys are detected correctly. This error could be happening in more connections, and I don’t know if it is being investigated. We have fixed it in the connections that affected us with a client, but we don’t know if there could be more affected. If it is normal and the “\<” character has been replaced by another one, we would like to know which one it is to adapt the scripts. Best regards * * * ---

_Answer by Javier Pozuelo on 20 September 2023_ Hello, The “\>” and “\<” operators work correctly when used in a condition, but you are correct, they are not highlighted on the code. We will report this UI bug to our engineering team. Thanks for the heads-up! Kind regards, Javier Pozuelo * * *