From 15db5d874eaff58320a8cb4303ada2fff864bec3 Mon Sep 17 00:00:00 2001 From: Norman Abramovitz Date: Sat, 17 Oct 2026 20:13:23 -0700 Subject: [PATCH] docs(deploy): list the job tracking limit in CF config #6018 added ASYNC_JOB_TRACKING_LIMIT_IN_MINS to config.example, config.dev, the Helm chart and the deploy docs, but not to the config.properties the CF package ships, so a CF operator reading it would not learn the setting exists. It is now listed there, commented out at its default, with how to set it on a running app. Refs #6002 --- deploy/cloud-foundry/config.properties | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/deploy/cloud-foundry/config.properties b/deploy/cloud-foundry/config.properties index 41039d2a64..f2561aa2bc 100644 --- a/deploy/cloud-foundry/config.properties +++ b/deploy/cloud-foundry/config.properties @@ -3,6 +3,12 @@ DATABASE_PROVIDER=sqlite HTTP_CONNECTION_TIMEOUT_IN_SECS=10 HTTP_CLIENT_TIMEOUT_IN_SECS=30 HTTP_CLIENT_TIMEOUT_MUTATING_IN_SECS=120 +# Minutes the browser follows a background operation (a slow service +# broker, a delete) before it stops checking; the operation carries on in +# Cloud Foundry. Defaults to 60; at least 1; over 360 (6 hours) logs a +# warning; 1440 (a day) or more uses 360. On a running app: +# cf set-env console ASYNC_JOB_TRACKING_LIMIT_IN_MINS 120, then restage. +#ASYNC_JOB_TRACKING_LIMIT_IN_MINS=60 SKIP_SSL_VALIDATION=true CONSOLE_PROXY_TLS_ADDRESS=:443 CONSOLE_CLIENT=console