Item Click workflow unresponsive when Relation “is not empty” (bug?)

[Daniel_Jenkins]

Issue Overview:
I’m experiencing an issue where an Item Click workflow on a list becomes completely unresponsive for any row where the Relation column (“Existing Support Relationship is not empty”) resolves as true, regardless of the data in the related row. If the Relation is empty, the workflow fires as expected.

Steps to Reproduce:

1. Create a list from any table (for example, Artists).
2. Add a Relation column, matching against a second table, single match.
3. Attach a workflow (App Interaction) to the list row, with a top-level condition: Relation “is not empty”.
4. Assign this workflow to “Item Click” in the list’s settings.
5. In Preview:
   • Clicking a row with an empty Relation works – workflow triggers.
   • Clicking a row where Relation is not empty does nothing – row is not clickable and the workflow never runs.

Key Observations:

• The unclickable state is strictly tied to “Relation is not empty”.
• The actual data in the related row doesn’t affect this (I confirmed by toggling values).
• No errors are thrown, and the cursor does not change on hover for affected rows.

Additional possibly-related issue:
Workflows sometimes revert to “Untitled workflow” or disappear after minimal engagement or navigation away from Glide Builder, with previously saved logic and steps lost.

Has anyone else run into this or found a workaround? Is this a known bug? Any help appreciated.

[Darren_Murphy]

I just tested this, and it works as expected.

Could you perhaps add some screenshots to show how you have everything configured?
Perhaps we can spot something that might not be obvious to you.

[Daniel_Jenkins]

Oh trust me, nothing is obvious to me…! You are very kind to take a look!
Here are screenshots of data sheets and workflow. I’ll try to add some config pieces, too…let me know what you’re missing! Many thanks in advance!!

Trying to populate artists rows in Support Relationships Table when a new user is onboarded through glide interaction. The “Heart Toggle” will live in the description and visually toggle status from the default “Available to support” to “Supporting”. We’ve wired that before and got it going. Just trying to solve the user data import at the moment… Thanks again!!