TriggerSleepAction: the dangers using it alone?

I've been searching on the forum and I've read that TriggerSleepAction() could cause desyncs because of lag.

I know that PolledWait() uses a timer in conjunction with TriggerSleepAction()
But, all I really want is a very short delay used for a loop without the overhead of PolledWait(). How much of a risk am I taking by using TriggerSleepAction()? Are there certain situations where TriggerSleepAction() is fine and some where it is not?

In my current situation, I would be using a short TriggerSleepAction() constantly.

TriggerSleepAction wont last shorter than polledwait. Minimum wait time is around.. 0.25 s (ithink). For shorter durations, avoid using triggersleep and use timers.

I realize that timers will give me much shorter, exact waits, but I don't need an exact wait, I only need a short one, about the length of a minimum TriggerSleepAction. I'm wondering though about the ramifications of using many TriggerSleepActions() in regards to desynchronization.

On short waits polledwait is the same as triggersleep in time. So dont use triggersleep.

I does desync, but only rarely on long waits when someone lags in between.

Never heard of dysnchs with TriggerSleepAction, if a player lags then the wait should stop for all players until the lag is over.

TriggerSleepAction doesn't have any direct relationship with desyncs or lag

Also for such a short wait I'd use TriggerSleepAction(0) instead of PolledWait, because polled wait just adds the overhead of a new temporary timer and internally still calls TriggerSleepAction.

Well, it doesn't, that's why they made PolledWait. I remember earlier versions of my EoW map, if you got that "waiting for players" crap, your hero would revive a lot sooner because I used the regular wait.

Thats true, but isnt triggersleepaction(0) about the same time as triggersleepaction(0.2) which means it doesnt make any difference at all which you use, besides that it doesnt wait if a player lags at that moment (which is.. rather unlikely but could happen)

By the way don't use regular PolledWait, it has a leak. Better fix the leak and then use it.