Bulk deploy fails silently when deploying from docker image

[dan5602]

To Reproduce

1. Go to project > environment
2. Click select all (I have four total applications, so I deselected one, as I only want to deploy/update three)
3. Bulk Actions > Deploy > Confirm
4. '3 services deployed successfully' - but as far as I can tell none of my running docker images get updated

If I go into each application individually and hit Deploy - then application gets updated as expected.

Dokploy Version v0.28.0

Current vs. Expected behavior

I expect all selected applications in bulk actions to be updated to the lastest image when bulk action > deploy is executed.

Provide environment information

Operating system: Version v0.28.0
Dokploy Version v0.28.0

Which area(s) are affected? (Select all that apply)

Application

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

No response

Will you send a PR to fix it?

No

[Siumauricio]

@dosubot review

[dosubot]

Issue Review: Valid Bug - Architectural Limitation

This is a confirmed valid bug caused by the async nature of Dokploy's deployment queue architecture.

Root Cause: The deploy mutation returns immediately after queuing the job, not after deployment completion. The bulk deploy counts successful mutation calls (jobs queued) rather than actual deployments completed.

Not Docker-specific: While reported for Docker images, this affects all deployment types. Docker images may be more susceptible due to additional failure points (registry auth, image pulling).

Related Issues:

• #3522 - Docker images with latest tag not updating
• #2910 - Stack services show success but run old versions
• #1626 - Bulk actions for databases (fixed in #1629)

Workarounds:

1. Check each application's Deployments tab after bulk deploy to verify completion
2. Use individual deploys to see real-time logs for critical deployments
3. Verify Docker images were updated: docker inspect <container> | grep Image

Recommended Fix: Modify bulk deploy to either wait for worker completion or implement WebSocket/polling for real-time deployment status tracking.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}