I have an async function which does some operations, and alongside calls two APIs but without the await keyword.
Now the widgets that are dependant on the response of these APIs are seen in continuous loading state even after the function has trigged and the APIs have come back successful.
This happens only in Deployed mode and used to work before.
Connect the response of these APIs to some widget, I test with the input widget
Now deploy the App
You will see that the widgets dependant on those APIs are seen in loading state, but from the network tab I was able to verify that the APIs have completed successfully and return response.
sneha122
commented
2 months ago
Is there an existing issue for this?
Description
I have an async function which does some operations, and alongside calls two APIs but without the await keyword. Now the widgets that are dependant on the response of these APIs are seen in continuous loading state even after the function has trigged and the APIs have come back successful.
This happens only in Deployed mode and used to work before.
Slack Thread here: https://theappsmith.slack.com/archives/C040LHZN03V/p1726054005869429
Steps To Reproduce
awaitkeywordYou will see that the widgets dependant on those APIs are seen in loading state, but from the network tab I was able to verify that the APIs have completed successfully and return response.
Public Sample App
No response
Environment
Production
Severity
High (Blocker to building or releasing)
Issue video log
No response
Version
Internal Instance - Nightly Build