<p>We are using knative to serve a nodejs app (with express) that would execute workflows and return back the results of execution. The app would have to execute workflows which could take minutes (if not hours) to finish executing. </p>

<p>After invoking the app, execution stops after a certain time (approximately 14min) with the status: 
<code>upstream request timeout</code></p>

<p>We modified the timeout accordingly for express and it seemed to have a slight effect, but not as much as needed. We used the following guide as baseline <a href="https://github.com/knative/docs/tree/master/docs/serving/samples/hello-world/helloworld-nodejs" rel="nofollow noreferrer">https://github.com/knative/docs/tree/master/docs/serving/samples/hello-world/helloworld-nodejs</a></p>

<p>Is there a config value that can be modified that would increase the execution of the app itself (perhaps a timeout value)?</p>

Vedo
<p><strong>UPDATED (25/6/19):</strong></p>

<p>As per <a href="https://github.com/knative/serving/pull/4196" rel="nofollow noreferrer">https://github.com/knative/serving/pull/4196</a>, in Knative v0.7, you can now specify <code>MaxRevisionTimeoutSeconds</code> which can be any integer. <code>timeoutSeconds</code> must be less than or equal to <code>MaxRevisionTimeoutSeconds</code>. <code>timeoutSeconds</code> defaults to <code>300</code>.</p>

<p><strong><em>OLD</strong>:
You can change <code>timeoutSeconds</code> (which I believe defaults to 300 seconds):</em></p>

<pre><code>apiVersion: serving.knative.dev/v1alpha1
kind: Service
metadata:
  name: my-app
  namespace: default
spec:
  runLatest:
    configuration:
      revisionTemplate:
        spec:
          timeoutSeconds: 300
          ...
</code></pre>
