fix(notify): open configured web run pages from ntfy

This commit is contained in:
2026-10-21 13:05:10 +01:00
parent 870c70aefa
commit 9ee2e003bf
12 changed files with 201 additions and 14 deletions
@@ -98,9 +98,16 @@ fails. Nothing else notifies — a queued, running, succeeded, canceled or inter
run sends nothing. You do not author these; they are the operator default, so a run
you never wired still reaches the operator.
The payload names the run and its pipeline and carries a `click` action
`pipelines://run/<id>` that opens that run in the Android app (the app declares the
scheme). A run that stays waiting is not republished on a read or restart, and a
The payload names the run and its pipeline. When the operator configures
`PIPELINES_WEB_PUBLIC_URL` on the server, run notifications and stage hooks carry
the authenticated web link `<origin>/runs/<id>`. Native installs default this to
their advertised web address; custom/VPN domains require the operator's actual
phone-reachable URL. Never use the API listener or ntfy URL, nor put credentials
in the click link. Existing Android-only installations without that setting keep
`pipelines://run/<id>`. Invalid origins omit the link and log a warning. Existing
delivered alerts are not rewritten. Do not change service settings or send a test
notification merely to author a workflow. A run that stays waiting is not
republished on a read or restart, and a
stage `notify` policy that already covers the same event (`on=waiting`, or a failure
hook) suppresses the run-level default, so one genuine event means one notification.
A delivery failure is logged, never fails the run, and is not retried.
@@ -110,4 +117,3 @@ a run waiting for a decision, then a failed run, then a run that finished since
operator last looked. It is derived from the run events the server already pushes
(no extra request), an entry clears when the run is resolved or the operator opens
it, and it can be deliberately dismissed. It is not a new place to start a run.