fix(runs): honest empty state — feature off vs. no runs yet
Some checks are pending
Security / Security check (push) Waiting to run

The empty state unconditionally claimed background runs were
switched off, even on hubs where the operator had enabled them.
The hub now reports the flag on the list RPC (detached_enabled);
the hint picks the truthful variant.

Signed-off-by: flemming-it <stefan.a.flemming@googlemail.com>
This commit is contained in:
flemming-it 2026-07-18 00:20:43 +02:00
parent 5aa69104e7
commit ae97b88257
7 changed files with 34 additions and 10 deletions

View file

@ -1783,6 +1783,7 @@
"runsReloadTooltip": "Reload the runs list",
"runsEmptyTitle": "No background runs",
"runsEmptyHint": "Runs that keep working in the background while you do something else appear here. The feature is optional and off by default — the guide shows step by step how to turn it on.",
"runsEmptyEnabledHint": "Background runs are switched on — none has been started yet. Start a flow with the \"run in background\" option and it will appear here.",
"runsEmptyGuideButton": "Open the guide",
"runsCancelButton": "Cancel",
"runsCancelSignalled": "Cancel signalled for {flow}.",