Dokploy / Dokploy/dokploy

Schedule jobs should trigger notifications on failure

Open
#4,210 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
37.4k
Forks
3k
Avg merge
1d 3h
Merged PRs (30d)
73

Description

What problem will this feature address?

Currently, scheduled jobs in Dokploy do not trigger notifications when they fail.

Even though logs are created, there is no way to get alerted via existing notification providers (Discord, Slack, etc).

Expected behavior:

  • Trigger notification when a scheduled job fails
  • Ideally include logs or error output

This would make scheduled tasks production-ready.

Describe the solution you'd like

I’d like scheduled jobs in Dokploy to trigger notifications when they fail, similar to how deploy and build errors are handled.

Specifically:

Add a new notification event for scheduled job failure
Send alerts through existing providers (Discord, Slack, etc.)
Include useful context in the notification:
job name
timestamp
exit code
error logs (or a link to logs)

Optionally:

Support notifications on success as well (configurable)
Allow per-job notification settings

This would make scheduled tasks much more reliable in production, since failures wouldn’t go unnoticed.

Describe alternatives you've considered

.

Additional context

No response

Will you send a PR to implement it?

No

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named. Start by tracing how scheduled-job failures are recorded and how deploy and build errors create notification events, then inspect the existing Discord and Slack provider paths. Done means a failed scheduled job emits the new event through existing providers with the requested job context and error information.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend, devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.