Skip to content

Handle permission denied errors gracefully in collector health (fixes #150)#154

Merged
erikdarlingdata merged 1 commit intodevfrom
feature/fix-permission-denied
Feb 19, 2026
Merged

Handle permission denied errors gracefully in collector health (fixes #150)#154
erikdarlingdata merged 1 commit intodevfrom
feature/fix-permission-denied

Conversation

@erikdarlingdata
Copy link
Owner

Summary

  • Permission errors (SQL 229/297/300) now log as PERMISSIONS status instead of ERROR
  • Don't increment ConsecutiveErrors — status bar won't show "erroring" for permission issues
  • Collection health grid shows NO_PERMISSIONS when a collector has only permission errors
  • Error message still visible so users know which grants are needed

Test plan

  • dotnet build -c Debug — 0 warnings, 0 errors
  • Connect with a limited-permission account, verify running_jobs shows NO_PERMISSIONS instead of FAILING
  • Verify status bar doesn't flag permission errors as "erroring"

Fixes #150

🤖 Generated with Claude Code

…150)

Permission errors (SQL 229/297/300) now log as PERMISSIONS status instead
of ERROR. They don't increment ConsecutiveErrors or show as FAILING in
the health grid. Collection health shows NO_PERMISSIONS when a collector
has only permission errors, with the error message still visible so users
know which grants are needed.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@erikdarlingdata erikdarlingdata merged commit 9f13d9e into dev Feb 19, 2026
3 checks passed
@erikdarlingdata erikdarlingdata deleted the feature/fix-permission-denied branch February 19, 2026 16:28
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.

1 participant