We're starting to use shell scripts extensively in our self hosted instance.
I've noticed shell script exit after 60sec, without returning any response (.data is empty and contains no return data).
Is this by design? any way to circumvent this?
The server log indicates the complete shell command does execute fully, it's just that the UI is "declaring" timeout after 60 seconds.
{"pid":72,"requestId":"XXXX","message":{"ipAddress":"XXXX","userSid":"XXXX","orgSid":"XXXX","resourceName":"XXXX,"resourceType":"shell","environment":"production","queryHash":"XXXX","isPreview":false,"context":"app","responseSize":2132,"userError":false,"retoolHeaders":{"x-retool-dbconnector-hash":"fab1e44df3f48f15"},"dbconnectorType":"","type":"QUERY_COMPLETE","timeTakenMillis":"93,138.00","startTime":"57,115,138,128,897","endTime":"57,208,276,887,702"},"level":"info","timestamp":"2023-06-08T17:03:39.451Z"}
Our retool pod already has the DBCONNECTOR_QUERY_TIMEOUT_MS : 1800000 environment variable set
The issue was resolved by setting our retool environment k8s ingress timeouts