Skip to content

Move "no tasks in running state" log to debug level#786

Merged
lucaslorentz merged 1 commit intomasterfrom
fix/no-tasks-log-to-debug
Mar 12, 2026
Merged

Move "no tasks in running state" log to debug level#786
lucaslorentz merged 1 commit intomasterfrom
fix/no-tasks-log-to-debug

Conversation

@lucaslorentz
Copy link
Owner

Summary

  • Demotes "Service has no tasks in running state" from WARN to DEBUG
  • This warning fires every polling interval for services with no running tasks (e.g. when using Sablier to stop idle services), flooding logs
  • A service having no running tasks is a normal operational state, not something that warrants a warning

Fixes #705

Test plan

  • All tests pass

🤖 Generated with Claude Code

This warning fires every polling interval for services with no running
tasks (e.g. when using Sablier to stop idle services), flooding logs.
Since a service having no running tasks is a normal operational state,
demote it to debug.

Fixes #705

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@lucaslorentz lucaslorentz merged commit 86d6dd5 into master Mar 12, 2026
3 checks passed
@lucaslorentz lucaslorentz deleted the fix/no-tasks-log-to-debug branch March 12, 2026 07:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Question] Logs get filled with "Service has no tasks in running state" when using Sablier module

1 participant