Presumably they mean from the OS settings. As an example, I recently dealt with a failing DisplayPort to HDMI adapter whereby, above a certain video resolution that was below even 1080p60, it would just give me no video and/or the OS would just straight-up fail to actually change video mode.
That being said, it’s worth noting that Wayland vs X11 can make a difference in this regard - from my experience, changing your desktop resolution on X11 always changes the actual video mode being output to your monitor since Intel graphics on Linux specifically do not support upscaling the desktop resolution via the GPU on external displays unlike AMD and Nvidia graphics (something I found out the hard way).
But on Wayland, especially on GNOME, it can sometimes be ambiguous if reducing your desktop resolution is actually reducing the resolution being output to your monitor or if your GPU is then upscaling that lower resolution to your monitor’s native resolution, negating the bandwidth savings from running that lower resolution.
Regardless, if you can get it working with a lower resolution, then the next thing to try are various tricks to reduce bandwidth without reducing resolution, e.g. a custom resolution that’s simply the same as your panel’s native but with reduced blanking, and/or even just straight-up reducing the refresh rate since it is a 144Hz monitor.
One thing to note is that the cvt command only understands reduced blanking for refresh rates that are multiples of 60, so either just use 120Hz or create a custom modeline yourself, perhaps using the Windows program CRU to figure out the necessary timings (you can’t apply CRU’s settings via WINE, but it works fine for calculating the necessary timing information - just note that this monitor might use DisplayID and I have no idea how that’ll impact things).
…that being said, because this monitor also supports AdaptiveSync, it’s very possible that making a custom resolution on Linux will break that since I have no idea of xrandr even has a way to work with VRR (assuming AdaptiveSync even works at all?)