This topic was automatically generated from Slack. You can find the original thread here.
I have experienced issues with the search feature within workflows, when I want to find a variable to use it, typing the variable’s name shows empty result even though it should. I’ve had to rely on the browser native search (cmd+f) feature to search properly.
This has been a pain, my client decided not to use Pipedream because of that. 
Hi , thanks for sharing! I don’t totally follow which search you’re referring to. Is it this one in the screenshot below?
Thank you for sharing! Will share with the team
Interesting, I wonder if there is a prop type mismatch that’s causing this. At first I thought maybe it was a nesting issue, but that doesn’t appear to be the case
I tried a few things and didn’t notice a clear pattern either. It worked when I expected it to fail :shrug:
Can you confirm if the prop types match? As in, is the prop you are looking for the same as the prop in which you’re searching? (Type could be integer, string, object, etc)
FYI I figured out the spaces between the words in the object keys (steps.trigger.event…) are breaking the search
Interesting, I wonder if a backslash would help or not
Oh lemme try, I have an example wired up
Did you mean a \ in the search, or in the referenced key?
In the search
Yeah, bummer
This is a legendary-level bug, I bet it’s there since the beginning, might have made believe a lot of people that pipedream doesn’t work well
Nice finding, totally makes sense to me, i never use spaces, programming background and all, but my clients… 
Agreed!
And nice finding, Danny!
