I don't personally take advantage of Celigo's offer to use existing steps when adding a lookup to a flow, but maybe others do?
I would like a way to turn this feature off, this could be a user profile preference?
Other than being distracting and unwanted, here's a real, evidence based reason:
Each keystroke triggers a request to the mother ship for suggestions, each one! LOL
For me to create that simple lookup and type a description generated 168 HTTP requests to Celigo and somewhere around 5MB of network traffic. It also slows down my browser so my typing has latency, you know ... l...a....t....e....n....c...y
Sure, subsequent keystrokes seem to cancel the previous pending request, but at what stage? How much bandwidth is already being used? I'd think Celigo's AWS bill may be impacted as well 
Please give us an option to turn this off. Don't want the feature, it doesn't help me, it wastes resources and creates a degraded user experience.
2 Likes
Hey @steveklett. Just a quick note that @nileshkumar on our PM team is working with our design and research group to investigate further.
1 Like
Hey @tonycurcio53
We're currently analyzing the issue and will be collaborating with @nileshkumar to determine the best fix. We'll share an update as soon as we have more details on the resolution and expected release.
Hi @steveklett
We’ve introduced debounce logic with a delay between keystrokes to reduce the number of API calls made while typing in Description and Name fields. This change significantly cuts down on unnecessary network traffic, improves browser responsiveness, and reduces backend load.
We hope this improvement noticeably enhances your experience. We’d love to hear your thoughts on it.
Please keep the feedback coming - it helps us make the platform better for everyone!
Thanks
Nilesh.
1 Like
Hi @nileshkumar,
I'm glad to hear about this. Are the changes live?
Hi @steveklett
Yes, the changes are live.
Please do verify from your end and let me know your thoughts.
Thanks
Nilesh.
Hi @nileshkumar,
It's better, and I appreciate the work to improve things, but it still has issues. There is an initial delay when the Name field gets focus, which is odd because I haven't typed anything yet so is it retrieving EVERYTHING? I think not, because as I type more it blocks again while it pulls down more data rather than client filtering the list of everything pulled down initially. That or maybe it's being wasteful and always pulling data from the server rather that filtering on the client.
It's also just plain problematic that what should be a background http operation is blocking UI code. When you type in a google search box the input isn't blocked while the browser fetches suggestions.
I would prefer the feature simply didn't exist or could be turned off as a preference.
