SOLVED 

 

• I’m using Paths after the Drive step to handle:

   

  1. Files that exist but are not in the shared drive

  2. Files that don’t exist or are not shared with the Zapier-connected account (fallback scenario)

The Drive step is set as follows:

• ✅ “Successful if no search results are found” = True

But when the file isn’t shared (thus not accessible), the Drive step throws an error like:

The app returned "File not found: [ID]" and reschedules the zap

As a result:

• The Zap halts at this step

• The fallback path is never triggered, even though it’s configured correctly

• I cannot send the appropriate fallback email or handle the logic gracefully

I’ve verified that:

• The fallback path has no additional conditions and is correctly configured as a catch-all, no inputs from the this Drive block in the fallback option. 

Expected behavior:

If the Drive step errors due to a file being unshared, it should not stop the Zap — especially if fallback logic is in place. Since I’ve set the step to not stop on failure and to consider no result as success, I’d expect it to proceed to the fallback path.

What I need:

• A way to ensure the Zap continues into the fallback when the file is unshared

• Or a fix so that the fallback path can handle the missing/unauthorized file scenario

Let me know if any additional logs or screenshots would help — happy to provide.

Thanks!