in our project we have a few backend workflows that take more than a few seconds to finish. These workflows are for example triggered via a “Save to Microservice”-action of a table.
For long-running workflows (perhaps ~60s) it is possible that the workflow finishes correctly, but the APPS frontend will continue to show a spinning “Save Changes” button and will never finish. Only after a reload of the App the correct (updated) data is shown.
Is it possible that some websocket, reverse proxy or other tooling has a timeout defined that leads to this behavior? Who would be able to change this?
(I know that we had the same issue for non-Apps issue with calling a microservice workflow endpoint directly where DevOps had to increase the reverse-proxy timeouts to allow requests to take more than the default of 60s… Is this perhaps similar since we also use “saveToMicroservice” here?)