Filter Condition Failing Due to "Null" Value Even When Data Exists – Possible Caching Issue?
Hi Zapier Community,
I'm facing a strange issue in one of my Zaps where it seems like a filter condition is not working as expected, and it might be related to caching or how test data is stored.
🔧 Context:
I'm using a Zoho CRM Find Module Entry step to locate a lead based on the email ID.
The response includes an Entry ID when a match is found.
Then, I’ve added a Filter step with the condition: Continue only if Entry ID exists.
🧪 The Problem:
In manual test data, the Entry ID is clearly present.
But when I run the entire Zap as a test run, the filter step fails.
Zapier shows the condition internally as: If null exists → then continue …which doesn’t make sense because I’m referencing a field that should contain the actual Entry ID, and it did in the previous step.
I've attached a screenshot showing this exact issue, where it looks like Zapier somehow replaces the expected dynamic value with null during the filter evaluation.
❓What I Want to Understand:
Is this behavior related to Zapier’s caching of test data?
Why would a field that clearly exists during a Find step result in a null value during the Filter step?
Has anyone else experienced this issue — and is there a known workaround?
Any help would be greatly appreciated, as this is impacting production workflows.
Thanks, Aditya
Page 1 / 1
Hi @puredesingsolution
The Zap Filter step condition is working as expected.
Zap step 4 attempts to find entries.
If 0 entries are found, then the Path Filter condition will not be met and the Zap Path will be filtered out.
In your live Zap Run check the DATA OUT from Zap step 4 to see if any entries were found.
However, as you can see in the Data Out of Step 3, the Entry ID is definitely present — the Find Module Entry step is successfully returning a result.
But still, in Step 6, the Path/Filter condition is not passing.
To troubleshoot further, I checked the filter condition details — and surprisingly, it shows something like:
If null exists → then continue
This is strange because I’ve selected the dynamic value from Step 4 (which contains a valid ID), yet it’s being interpreted as null in the filter.
I’ve attached the screenshot to show this clearly.
Would love to know if this is a known issue or if I’m missing something subtle here.
Thanks again! Aditya
This post has been edited by a moderator to remove personally identifiable information (PII). Please remember that this is a public forum and avoid sharing sensitive details.
@puredesingsolution
How is the Filter condition configured for Zap Step 10?
Path B Step 8 the filter condition uses data from Zap step 4, not Zap step 3.
@puredesingsolution
Issue with the Path Filter conditions may be related to the data being an array.
You can try converting the array values to text using this Zap action: Formatter > Utilities > Line Items to Text
Then use the output from the Formatter step as part of the Filter step condition evaluation.
🔟 Regarding Zap Step 10 (Filter Condition): The filter is configured as follows:
If Entry ID 1 (from “Find Lead” step) AND Entry ID 2 (from “Find Contact” step) do not exist, → then create a new record in Zoho CRM.
However, as shown in the screenshot I’ve attached, Zapier is evaluating both conditions as:
If null does not exist AND null does not exist → then continue
This is incorrect — because both Entry ID 1 and Entry ID 2 actually exist in the previous steps. Their values show up correctly in the "Data Out" of their respective steps.
So the filter should evaluate the actual Entry IDs, not null.
✅ Regarding Your Second Point: Yes, you're absolutely right — the data out for Zap Step 4 clearly shows that an entry was found and an Entry ID exists. But the filter condition still treats it as null, which is causing the condition to fail unexpectedly.
It seems like Zapier is not correctly mapping the dynamic fields at runtime, and replacing them with null, even though the data is available.
and here is an another screenshot where it says that Your path would have continued for this test data. so why it is coming as null when i run with the same test data??
Could this be a bug or data parsing issue in how Zapier handles dynamic values in filters?
Let me know if I can provide more detailed logs or a shared version of the Zap for better visibility.
Thanks again! Aditya
@puredesingsolution
Did you try this suggestion?
Issue with the Path Filter conditions may be related to the data being an array.
You can try converting the array values to text using this Zap action: Formatter > Utilities > Line Items to Text
Then use the output from the Formatter step as part of the Filter step condition evaluation.
here you can see i have used utilities and then use the output from the formatter step as part of the filter This is path condition and it still says null Exists, why is null coming ? Even formatter is working fine, but in condition i get this null everytime?
Thanks again for the suggestion!
I added the Formatter > Utilities > Line Items to Text step as advised, and used its output in the Filter step condition.
🧪 Here’s what happened:
When I test the filter step individually, it says: ✅ "Your path would have continued for this test data."
However, when I run the complete Zap as a test, it still evaluates the filter as: ❌ "If null exists → then continue", …which means the dynamic value is still being replaced with null.
🔍 Additional Info:
The original data from the "Find Module Entry" step is not an array at the root level — it contains a single object with an Entry ID.
I’ve attached both screenshots: one from the test data showing it should pass, and one from the full Zap run showing null instead of the expected ID.
So now I’m confused — if the Formatter step is returning valid text and the condition is properly configured, why is the filter still interpreting it as null during the full Zap run?
Is this possibly:
A Zapier runtime bug where dynamic values aren’t being resolved during actual runs?
Or an issue with how Zapier handles test data vs real-time execution?
Looking forward to your insights — this is getting close, but still not working reliably in real runs.
Issue may be related to how your Zoho CRM Find Entries steps are configured.
Try using the default value for the field: If multiple search results are found.
To clarify, data is returned from the Zoho CRM “Find Entries” steps as an array of items. You can tell by the numbered line items nested under Entries. (screenshot)
Hi @puredesingsolution
I’m having a similar problem, did you find a resolution?
Hi @msprop,
You're experiencing an issue similar to one reported by another user. While I don't have the resolution, I'd be happy to troubleshoot. Could you share more details, such as the issue, error messages, apps your Zap uses, and steps you've tried? The more context you provide, the better I can assist you in finding a solution
