Sonat

If someone can tell me if problem is resolved with the new update.

i'm ok with the fact that is not his priority, i mean , i can imagine the amount of work to maintain something like wrobot.
But just one word from him like this "yea guys i checked it and i confirm its a bug but i have stuff to fix before this" and mark this thread status as "confirmed".
Communication is key here.

he will fix it soon because bugs like that appeared before patch 7.2 too, but as you just said: it is not his priority
best thing to do: use another bot for rotation (there are plenty) or learn how to play your class... i know it is hard to play without mistakes for 5 hours straight but you have to find a solution ;)

So i confirm it's a bug or whatever you call it because it always happen when you meet the conditions.
i did test all possible options for wrotation (even the advanced one) on 3 differents DPS classes (2 cac and 1 ranged).
i write my own rotations but i also test with some random from the forum and i can say my rotations works everywhere with no problem 
If a Boss had more than 2148M health (full life or not), rotation engine doesnt work and magically begin to work itself when boss's life goes under 2148M. Nothing to do, just wait for it.
It's a heavy problem because in the nighthold, LFR Guldan has more than 2148M and if you are in a 2/3/9 roster, some HM Boss got more than 2148M life and all boss on MM got more than 2148M.
I fear about Tomb of Sargeras, because i believe majority of boss will get more than 2148M life.
So please @Droidz, say something about this, because its a real issue..
Thank you.

Could it be that the underlying code is using an long integer somewhere that tracks the targets health? And exceeds the 2147483647 max value for C#?
https://msdn.microsoft.com/en-us/library/296az74e.aspx
Perhaps initializing the var with UInt32 instead of int32? All speculation on my part...
https://msdn.microsoft.com/en-us/library/x0sksh43.aspx

So, its almost two weeks now this issue has been submitted, no words from dev and it began to be a real problem for me (and for some other users too i believe) because i use wrobot almost exclusively for rotation.
Don't get me wrong, i like Wrobot and Droidz but if we can have some news about this issue, it will be great.
Thank you

OK, just ran 2 wings and Guldan in LFR. It looks like the rotation will not start until the Boss reaches 2,140,000,000 health. That is as close as I could get watching the numbers roll down anyway.
Botanist = 2194M health - didn't start until a few seconds after pulling (saw it start right around 2140M)
Guldan - same thing (not sure what his starting health is)
Star Auger = 2140M health - started right away, but I remember having to wait in heroic last week (and the weeks before)
All the other bosses I tried started below 2140M and I had no trouble with any of them.