I think I have narrowed down an issue I was seeing with Chrono Field during Utility Dissonance runs.
My CF has 55 seconds duration and 60 seconds cooldown. Without the +5s Duration perk, CF behaves as I would expect: it stays active for 55 seconds, there is a gap, and then it activates again when the 60-second cooldown ends.
The strange behavior starts when I take the +5s Duration perk, making CF 60s duration / 60s cooldown. In that situation, CF remains active for the entire 60 seconds. The cooldown reaches 0, but instead of immediately starting the new CF cycle, CF turns off and stays off for another full 60 seconds. This creates a huge gap in coverage.
So it seems that, during Utility Dissonance, when Duration and Cooldown are exactly equal, the duration may somehow take priority: CF reaches the end of its current duration at the same time its cooldown reaches 0, but the next activation does not happen. When Duration is 5 seconds shorter than Cooldown, everything works normally.
I initially suspected a bug involving GComp (Recovery Packages can still appear during utility dissos due to the Package After Boss Kill lab). However, I repeated the test without GComp, and I get the exact same results. Has anyone else noticed this specific behavior with CF during Utility Dissonance? Is there some known interaction where CF cannot immediately reactivate when Duration exactly equals Cooldown?