Hey folks, I m facing some issues with custom loader. Everything was working in local server as I expected. After deploying in AWS environment, that loader behaviour looks strange. We have used boostrap multi select widget for displaying the unique values in the dropdown list getting from datalake. When we connect with datalake, we executing some SQL query to fetch the data from datalake. It took more than 3 to 4 mins. But, we could not display the loader till that time. But query was running in the background microflow. Microflow did not completes the process. That loader, executing upto 60 seconds only. After that, it does not work. Is there any other way to trigger this loader until the backend microflow completes the process ? Your suggestions are more welcomed Regards, Vijayabharathi V