Hey,
I have a component in my app that filters results (according to naming rules)
this component is now deprecated, and doesn't work properly.
I didn't build this app originally so I'm not sure how to address the issue, is anyone familiar with this component by any chance? and knows how to replace it to an updated version?
Hello @Yael_Cohen,
The issue could be related to a deprecated custom component that automatically refreshes or reloads after your code or query runs successfully. This behavior sometimes causes unexpected results or makes the flow harder to control.
As an alternative, I’d recommend switching to Retool’s built-in custom component framework. It’s more reliable, actively supported, and designed to integrate smoothly with queries, transformers, and state management. By using Retool’s latest component setup, you’ll have better stability, improved performance, and fewer chances of running into issues with auto-refresh or unexpected reloads.
2 Likes
thank you. I understand this requires coding skills, which I do not have 
Hi @Yael_Cohen,
We recommend solving this by upgrading to the new version that WidleStudioLLP recommends. Unfortunately, it does require recreating the component using the new process with custom code.
That said, the deprecated component should still work 
The fact that it is deprecated means it is not going to receive new features & updates, and it may be more prone to bugs. Are there any browser console errors?
2 Likes
where can I see if there are browser console errors?
@Yael_Cohen To check browser console errors, open Developer Tools (Right-click → Inspect → Console). Errors appear in red, warnings in yellow. On Mac, use Cmd + Option + I
Hello @Yael_Cohen,
Thank you for sharing the console screenshot. Based on the error details shown, the issue originates from your custom component code. In order to resolve this, you will need to review and correct the code implementation.
Once you identify and correct the error within your custom component, the problem should be resolved.
1 Like
Hi @Yael_Cohen,
I second @WidleStudioLLP's assessment of the error messages.
One option would be to use a coding tool such as an LLM to help you understand the code in the custom component you inherited.
Another option that may be easier is if you can describe the functionality of the component, in terms of inputs and outputs, I can see if we have a pre-build component in Retool that can be used to replace the broken custom component!
1 Like
Hi @Yael_Cohen,
Just wanted to check in and see if you were able to get some assistance from the a third party tool such as an LLM to help better understand the custom component or if you found any of our new or updated components to meet the need for your use case.
Any additional details you can provide would allow for me to better help!
Hey @Jack_T thank you so much for checking in.
I haven’t been able to do it on my own.. probably need a developer for that.
This component is used to filter the results of a query, over multiple tables. Kind of similar to the “filter” feature:
but the difference is that it’s not only affecting this specific table, but all of the dashboard.
This is how it looks:
Hi @Yael_Cohen,
Thank you for getting back to me!
So to confirm, there are multiple tables with different data, and this custom filter component is applying one or many custom filtering rules that affect all the tables on that page of the app, correct?
I was looking at the errors you shared to see if I could figure out what was going on. My guess is that there may be some hard coded HTML identifiers for child components inside the custom component.
Support for custom code falls outside my realm of knowledge for Retool support. My best recommendation would be to see if an LLM can use the code and error message to pinpoint what could be changed to fix those errors.
thank you, @Jack_T. I will try your suggestion.
1 Like