# Workflow looping is returning unexpected results
**URL:** https://community.glideapps.com/t/workflow-looping-is-returning-unexpected-results/78717
**Category:** Ask for Help
**Created:** [December 21, 2024, 2:02am UTC](https://community.glideapps.com/t/workflow-looping-is-returning-unexpected-results/78717 "2024-12-21T02:02:17Z")
**Posts on this page:** 12
**Page:** 1
### Author:  [@gabrielbrown](https://community.glideapps.com/u/gabrielbrown)
#### Post date: [December 21, 2024, 2:02am UTC](https://community.glideapps.com/t/workflow-looping-is-returning-unexpected-results/78717/1 "2024-12-21T02:02:17Z")
Hi,
I’m trying to automatically delete a row if a condition is met. I’m attempting to achieve this by using a scheduled workflow that loops through rows in a Glide table.
I have set up my workflow to loop through a database ‘Session Requests’ and filter where an If-Then-Else column ‘Deletion Request?’ is checked. (The “Deletion Request?” returns true when a Query column is empty).
However, when the workflow runs, it deletes all rows in the database. As pictured, despite only one row returning a true Deletion Request, the replay shows that Glide processed both rows as meeting the filtering conditions.
Maybe I’m missing something, and I’d appreciate your help!
Thanks
Session Request Database (before running workflow):
Workflow configuration:
‘Session Requests’ after running workflow:
Workflow replay:
---
### Author:  [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)
#### Post date: [December 21, 2024, 9:49am UTC](https://community.glideapps.com/t/workflow-looping-is-returning-unexpected-results/78717/2 "2024-12-21T09:49:33Z")
Can you share the configuration of the “Deletion Scheduled?” column please?
---
### Author:  [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)
#### Post date: [December 22, 2024, 12:35am UTC](https://community.glideapps.com/t/workflow-looping-is-returning-unexpected-results/78717/3 "2024-12-22T00:35:25Z")
Any chance your query relies on a datetime column?
---
### Author:  [@Andrew\_Davies](https://community.glideapps.com/u/Andrew_Davies)
#### Post date: [January 10, 2025, 5:08pm UTC](https://community.glideapps.com/t/workflow-looping-is-returning-unexpected-results/78717/4 "2025-01-10T17:08:33Z")
Hello there
I have this exact same issue. I am trying to set up a scheduled workflow which deletes redundant rows from a table so it doesn’t get too big. A redundant row is when a relation is empty (so all rows in the parent table that relate to that row are deleted).
My loop (which is sent to return only rows with the related column empty) - returns all rows.
See screenshots.
Any suggestions? I tried doing a count of relations, but that didn’t work.
Andrew
---
### Author:  [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)
#### Post date: [January 10, 2025, 9:20pm UTC](https://community.glideapps.com/t/workflow-looping-is-returning-unexpected-results/78717/5 "2025-01-10T21:20:36Z")
How is the relation created?
---
### Author:  [@NFNHello](https://community.glideapps.com/u/NFNHello)
#### Post date: [January 10, 2025, 11:59pm UTC](https://community.glideapps.com/t/workflow-looping-is-returning-unexpected-results/78717/6 "2025-01-10T23:59:27Z")
I had the same issue where my boolean that determined the loop was made based on an AI text to date column. Support said that the AI column wasn’t supported in scheduled workflows. I rebuilt the text to date manually and it worked as expected. I’m guessing that once you dig into your “QueryFacilitator” query, you might find what’s going on.
---
### Author:  [@Andrew\_Davies](https://community.glideapps.com/u/Andrew_Davies)
#### Post date: [January 11, 2025, 10:22am UTC](https://community.glideapps.com/t/workflow-looping-is-returning-unexpected-results/78717/7 "2025-01-11T10:22:28Z")
Thanks both
It’s a straightforward relation.
The “master” table splits a single JSON query into 50 rows using an index and query json columns based on the index (using Bob’s tip of getting all row IDs then find index)
As I need to record some extra information against each row, I have a relation to another table on a unique field that doesn’t change. I can’t add columns as the index value may change so the rows would change.
As the JSON is a list of sequential transactions, and I can only store 50 (which doesn’t matter. That’s plenty) - some drop off the bottom.
I want this workflow to delete the rows with no relation as they are not needed anymore.
That’s the crux of it at least!
---
### Author:  [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)
#### Post date: [January 11, 2025, 2:53pm UTC](https://community.glideapps.com/t/workflow-looping-is-returning-unexpected-results/78717/8 "2025-01-11T14:53:15Z")
Is there any where in your flow you reference something related to the users table?
---
### Author:  [@NFNHello](https://community.glideapps.com/u/NFNHello)
#### Post date: [January 11, 2025, 3:00pm UTC](https://community.glideapps.com/t/workflow-looping-is-returning-unexpected-results/78717/9 "2025-01-11T15:00:02Z")
Or User Specific Columns
---
### Author:  [@Andrew\_Davies](https://community.glideapps.com/u/Andrew_Davies)
#### Post date: [January 11, 2025, 6:57pm UTC](https://community.glideapps.com/t/workflow-looping-is-returning-unexpected-results/78717/10 "2025-01-11T18:57:15Z")
Nope - neither
---
### Author:  [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)
#### Post date: [January 12, 2025, 1:15am UTC](https://community.glideapps.com/t/workflow-looping-is-returning-unexpected-results/78717/11 "2025-01-12T01:15:26Z")
Might be worth reporting it in the beta Slack channel (if you’re there).
---
### Author:  [@Andrew\_Davies](https://community.glideapps.com/u/Andrew_Davies)
#### Post date: [January 12, 2025, 8:56am UTC](https://community.glideapps.com/t/workflow-looping-is-returning-unexpected-results/78717/12 "2025-01-12T08:56:46Z")
Will do.