OK feature maybe, bad implementation

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 :sweat_smile:

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 @tonycurcio

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.