Updated Successfully notification not received consistently

[begunfx]

Drydock version

1.5.0-rc.7

What happened?

Up until now I was not receiving any updated notifications successfully (appologies for not submitting a bug report on this - just realized it now), so getting some is an improvement. However, I seem to get them inconsistently. I updated my tdarr_nodes as an Update All and go no notification that they updated successfully, and I also updated a few individual containers and out of the three I only got one message.

I can confirm that I have the notifications configured correctly:

What did you expect?

See above

Steps to reproduce

See above

Relevant configuration

Logs

Installation method

Docker Compose

Docker version

24.0.1

OS / Architecture

Synology DSM 7

[begunfx]

Additional note: Calibre was the container I updated that didn't not send a updated successfully notification. See logs:

1
[07:57:31.452]
debug
trigger.docker.tmvault
Skipping update-available notification for mediavault_calibre-web (excluded-from-allow-list)
2
[07:57:31.446]
debug
trigger.docker.servicevault2
Skipping update-available notification for mediavault_calibre-web (excluded-from-allow-list)
3
[07:57:31.444]
debug
trigger.docker.servicevault
Skipping update-available notification for mediavault_calibre-web (excluded-from-allow-list)
4
[07:57:31.441]
debug
trigger.pushover.mobile
Skipping update-available notification for mediavault_calibre-web (changed=false, once=true, updateAvailable=false)
5
[07:57:31.439]
debug
trigger.docker.mediavault
Skipping update-available notification for mediavault_calibre-web (excluded-from-allow-list)
6
[07:57:31.438]
debug
trigger.docker.datavault
Skipping update-available notification for mediavault_calibre-web (excluded-from-allow-list)
7
[07:57:31.414]
debug
trigger.docker.tmvault
Skipping update-available notification for mediavault_calibre (excluded-from-allow-list)
8
[07:57:31.408]
debug
trigger.docker.servicevault2
Skipping update-available notification for mediavault_calibre (excluded-from-allow-list)
9
[07:57:31.406]
debug
trigger.docker.servicevault
Skipping update-available notification for mediavault_calibre (excluded-from-allow-list)
10
[07:57:31.403]
debug
trigger.pushover.mobile
Skipping update-available notification for mediavault_calibre (changed=false, once=true, updateAvailable=false)
11
[07:57:31.400]
debug
trigger.docker.mediavault
Skipping update-available notification for mediavault_calibre (excluded-from-allow-list)
12
[07:57:31.400]
debug
trigger.docker.datavault
Skipping update-available notification for mediavault_calibre (excluded-from-allow-list)
13
[07:57:01.851]
debug
trigger.docker.tmvault
Skipping update-available notification for mediavault_calibre-web (excluded-from-allow-list)
14
[07:57:01.845]
debug
trigger.docker.servicevault2
Skipping update-available notification for mediavault_calibre-web (excluded-from-allow-list)
15
[07:57:01.842]
debug
trigger.docker.servicevault
Skipping update-available notification for mediavault_calibre-web (excluded-from-allow-list)
16
[07:57:01.838]
debug
trigger.pushover.mobile
Skipping update-available notification for mediavault_calibre-web (changed=false, once=true, updateAvailable=false)
17
[07:57:01.814]
debug
trigger.docker.mediavault
Skipping update-available notification for mediavault_calibre-web (excluded-from-allow-list)
18
[07:57:01.812]
debug
trigger.docker.datavault
Skipping update-available notification for mediavault_calibre-web (excluded-from-allow-list)
19
[07:57:01.775]
debug
trigger.docker.tmvault
Skipping update-available notification for mediavault_calibre (excluded-from-allow-list)
20
[07:57:01.768]
debug
trigger.docker.servicevault2
Skipping update-available notification for mediavault_calibre (excluded-from-allow-list)
21
[07:57:01.765]
debug
trigger.docker.servicevault
Skipping update-available notification for mediavault_calibre (excluded-from-allow-list)
22
[07:57:01.763]
debug
trigger.pushover.mobile
Skipping update-available notification for mediavault_calibre (changed=false, once=true, updateAvailable=false)
23
[07:57:01.759]
debug
trigger.docker.mediavault
Skipping update-available notification for mediavault_calibre (excluded-from-allow-list)
24
[07:57:01.758]
debug
trigger.docker.datavault
Skipping update-available notification for mediavault_calibre (excluded-from-allow-list)
25
[07:51:38.684]
debug
trigger.docker.tmvault
Skipping update-available notification for mediavault_calibre-web (excluded-from-allow-list)
26
[07:51:38.679]
debug
trigger.docker.servicevault2
Skipping update-available notification for mediavault_calibre-web (excluded-from-allow-list)
27
[07:51:38.676]
debug
trigger.docker.servicevault
Skipping update-available notification for mediavault_calibre-web (excluded-from-allow-list)
28
[07:51:38.673]
debug
trigger.pushover.mobile
Skipping update-available notification for mediavault_calibre-web (changed=false, once=true, updateAvailable=false)
29
[07:51:38.670]
debug
trigger.docker.mediavault
Skipping update-available notification for mediavault_calibre-web (excluded-from-allow-list)
30
[07:51:38.669]
debug
trigger.docker.datavault
Skipping update-available notification for mediavault_calibre-web (excluded-from-allow-list)
31
[07:51:38.641]
debug
trigger.docker.tmvault
Skipping update-available notification for mediavault_calibre (excluded-from-allow-list)
32
[07:51:38.634]
debug
trigger.docker.servicevault2
Skipping update-available notification for mediavault_calibre (excluded-from-allow-list)
33
[07:51:38.631]
debug
trigger.docker.servicevault
Skipping update-available notification for mediavault_calibre (excluded-from-allow-list)
34
[07:51:38.628]
debug
trigger.pushover.mobile
Skipping update-available notification for mediavault_calibre (changed=false, once=true, updateAvailable=false)
35
[07:51:38.625]
debug
trigger.docker.mediavault
Skipping update-available notification for mediavault_calibre (excluded-from-allow-list)
36
[07:51:38.625]
debug
trigger.docker.datavault
Skipping update-available notification for mediavault_calibre (excluded-from-allow-list)
37
[07:51:08.247]
debug
trigger.docker.tmvault
Skipping update-available notification for mediavault_calibre-web (excluded-from-allow-list)
38
[07:51:08.241]
debug
trigger.docker.servicevault2
Skipping update-available notification for mediavault_calibre-web (excluded-from-allow-list)
39
[07:51:08.238]
debug
trigger.docker.servicevault
Skipping update-available notification for mediavault_calibre-web (excluded-from-allow-list)
40
[07:51:08.234]
debug
trigger.pushover.mobile
Skipping update-available notification for mediavault_calibre-web (changed=false, once=true, updateAvailable=false)
41
[07:51:08.231]
debug
trigger.docker.mediavault
Skipping update-available notification for mediavault_calibre-web (excluded-from-allow-list)
42
[07:51:08.230]
debug
trigger.docker.datavault
Skipping update-available notification for mediavault_calibre-web (excluded-from-allow-list)
43
[07:51:08.200]
debug
trigger.docker.tmvault
Skipping update-available notification for mediavault_calibre (excluded-from-allow-list)
44
[07:51:08.193]
debug
trigger.docker.servicevault2
Skipping update-available notification for mediavault_calibre (excluded-from-allow-list)
45
[07:51:08.190]
debug
trigger.docker.servicevault
Skipping update-available notification for mediavault_calibre (excluded-from-allow-list)
46
[07:51:08.188]
debug
trigger.pushover.mobile
Skipping update-available notification for mediavault_calibre (changed=false, once=true, updateAvailable=false)
47
[07:51:08.184]
debug
trigger.docker.mediavault
Skipping update-available notification for mediavault_calibre (excluded-from-allow-list)
48
[07:51:08.184]
debug
trigger.docker.datavault
Skipping update-available notification for mediavault_calibre (excluded-from-allow-list)

[s-b-e-n-s-o-n]

This has been addressed in the upcoming RC.

• Root cause: When Docker updates a container, it renames the old container (e.g., tdarr_node → tdarr_node_old) before creating the new one. The update-applied success event was being emitted against the original container name, but by the time it fired, the container had already been renamed — so the event was lost and no notification was delivered.
• Fix: Success events are now preserved across the Docker rename race, so the notification resolves correctly regardless of timing (6b5c1f72)

For the "Update All" scenario with your tdarr_nodes — this should now work consistently since each container's success event is tracked by its stable ID rather than its name. The next RC will be out shortly — please test both individual and bulk updates and let us know if notifications come through reliably.

[begunfx]

Still not seeing an updated successfully notification in drydock rc.15. See video:
https://drive.google.com/file/d/16hsIF5S50omexN7uL23p_HqGdjphtqNI/view?usp=sharing

[begunfx]

Still not seeing this notification consistently when containers get updated rc.18. See video reference:
https://drive.google.com/file/d/1nOfA9xuIYfH-LAHyKLDIlbJ7dR0oLkJV/view?usp=sharing

[s-b-e-n-s-o-n]

Fixed in feature/v1.5-rc19 (queued for v1.5.0-rc.19).

Root cause: the toast lived in 3+ separate handlers (ContainerUpdateDialog, useContainerSsePatchPipeline, ContainersGroupedViews, DashboardView), each gated on different state. Any one of them missing — operationId absent on the wire, view unmounted, batch-suppression dependency on a sibling component — silently dropped the toast.

What changed:

• New global useGlobalUpdateToast mounted at App.vue is the single source of truth for terminal update toasts. Survives route navigation.
• Backend stops coercing operationId/containerId to ''; the wire format is now honest about what's optional.
• SSE reconnect now sends Last-Event-ID (via query param, since browser EventSource cannot set headers) so the server-side ring buffer (5min TTL) can replay missed terminal events.
• Toast firing waits for the matching dd:sse-container-added/updated/removed event so it appears the moment the row's "Updating" badge clears (not on a hardcoded delay). 5s safety fallback for remote agents and deleted containers.
• Defensive hardening: singleton guard on the global handler, FIFO-bounded dedup map (cap 500), Last-Event-ID format validation server-side, HTML-strip on raw error text.

QA-verified locally on the qa-compose stack. Will land in rc.19.