Dossier Agent Stuck on File Search Step and Not Proceeding to Branch Logic - Need Help

Lauren G. · 2026-02-22T23:57:06.091Z

@Alon J. me again 🤪. I have a head scratcher that I am not sure is a bug or not. I have a “dossier” agent that wont go past the first step of searching for a file if it doesn’t find it even though the literal next step in the process is a branch between yes file found or no file not found. I literally cannot get it to move past the find file step … any ideas?

Dossier Agent Stuck on File Search Step and Not Proceeding to Branch Logic - Need Help | Lindy Community

11 comments

· Sorted by Oldest

Alon J.
·
·
Hey Lauren! Ah, good question - I don't believe this is a bug as if there is no file found, it errors out, which is intentional. I don't believe this is a way to not provide an error and stop the workflow if the file is not found. It's not hitting the condition because once there is an error, the workflow is stopped in its tracks, which results in not getting to the next step. I'll send a note to my team who may have an idea on an alternative solution here
Alon J.
·
·
Hey Lauren G. My colleague advised me that you can actually right click on the error and use that as the 'not found' option, which basically means if the action errors than do X. Having said that, I haven't tested this out myself. Do you have the link to the task URL for this instance? Happy to take a look as well!
Lauren G.
·
·
Hi hi Alon J. here is the link to the workflow. What I am trying to get it to do is ONLY continue if there isn’t a file already, it would make sense to run the process if we already have a dossier so I am perplexed how to accomplish this without that step before so I am all ears!
Georgiadis S.
·
·
Hey Lauren G.! I've run into this exact issue. The problem is that "Find File" throws an error when it doesn't find anything — it doesn't return a "no file found" result that your Condition can evaluate. The flow dies at the Find File step before it ever reaches the branch. Replace "Find File" with an agent step that has the Google Drive skill enabled. Have it search for the file and return a JSON response like {"found": true, "file": "..."} or {"found": false}. Agent steps don't error out on empty results — they always produce output. Then your Condition branches on the found value.
Lauren G.
·
·
Thanks Georgiadis S. that is an interesting work around I will try, though I do think we need some logic with find file action too
Lauren G.
·
·
Thanh P. how did you get around this? 👀
Thanh P.
·
·
Easy - add error handling. If it throws an error, it means nothing found, and then you branch off.
Thanh P.
·
·
3 dots on "find file" and add error handling
Lauren G.
·
·
And just move all the things I have there no file found there error handling instead?
Thanh P.
·
·
Yes
Lauren G.
·
·
Thank you Thanh P.! I feel so silly cause this was created before error handling so no idea how I made this work before without issue 🤦🏻‍♀️

Alon J.
·
·
Hey Lauren! Ah, good question - I don't believe this is a bug as if there is no file found, it errors out, which is intentional. I don't believe this is a way to not provide an error and stop the workflow if the file is not found. It's not hitting the condition because once there is an error, the workflow is stopped in its tracks, which results in not getting to the next step. I'll send a note to my team who may have an idea on an alternative solution here
Alon J.
·
·
Hey Lauren G. My colleague advised me that you can actually right click on the error and use that as the 'not found' option, which basically means if the action errors than do X. Having said that, I haven't tested this out myself. Do you have the link to the task URL for this instance? Happy to take a look as well!
Lauren G.
·
·
Hi hi Alon J. here is the link to the workflow. What I am trying to get it to do is ONLY continue if there isn’t a file already, it would make sense to run the process if we already have a dossier so I am perplexed how to accomplish this without that step before so I am all ears!
Georgiadis S.
·
·
Hey Lauren G.! I've run into this exact issue. The problem is that "Find File" throws an error when it doesn't find anything — it doesn't return a "no file found" result that your Condition can evaluate. The flow dies at the Find File step before it ever reaches the branch. Replace "Find File" with an agent step that has the Google Drive skill enabled. Have it search for the file and return a JSON response like {"found": true, "file": "..."} or {"found": false}. Agent steps don't error out on empty results — they always produce output. Then your Condition branches on the found value.
Lauren G.
·
·
Thanks Georgiadis S. that is an interesting work around I will try, though I do think we need some logic with find file action too
Lauren G.
·
·
Thanh P. how did you get around this? 👀
Thanh P.
·
·
Easy - add error handling. If it throws an error, it means nothing found, and then you branch off.
Thanh P.
·
·
3 dots on "find file" and add error handling
Lauren G.
·
·
And just move all the things I have there no file found there error handling instead?
Thanh P.
·
·
Yes
Lauren G.
·
·
Thank you Thanh P.! I feel so silly cause this was created before error handling so no idea how I made this work before without issue 🤦🏻‍♀️