# Gotchas When Using Window UUIDs

**URL:** <https://the.fmsoup.org/t/gotchas-when-using-window-uuids/5504>\
**Category:** Heads-Up!\
**Tags:** script, window\
**Created:** [June 10, 2026, 5:05am UTC](https://the.fmsoup.org/t/gotchas-when-using-window-uuids/5504 "2026-06-10T05:05:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bdbd](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/bdbd/32/620_2.png) [@bdbd](https://the.fmsoup.org/u/bdbd)\
**Post date:** [June 10, 2026, 5:05am UTC](https://the.fmsoup.org/t/gotchas-when-using-window-uuids/5504/1 "2026-06-10T05:05:49Z")

</div>

For whatever reason, script steps where you need to identify a window give you only one field to specify its title or its UUID. Avoid naming a window by another's UUID. Not that I think it's a good idea but it can be done. I am surprised no one caught this during testing, and even more surprised no one thought of this or thought it was important enough during design.

---

<div class="post-metadata">

**Author:** ![jwilling](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/jwilling/32/256_2.png) [@jwilling](https://the.fmsoup.org/u/jwilling)\
**Post date:** [June 10, 2026, 7:23am UTC](https://the.fmsoup.org/t/gotchas-when-using-window-uuids/5504/2 "2026-06-10T07:23:35Z")

</div>

I suspect it was a conscious decision on their end to avoid having to modify the UI or shape of the script steps that use the new Window UUID.

The way they did it, they just had to create/expose window UUIDs and then accept them in the same slot that the old window name goes and change the underlying function logic. There's a certain elegance/cleverness to the solution they picked, even though it's less explicit. And I usually prefer explicit, but i think the risk of misuse is low in this case.