Repository navigation
feat(jobs): support for good job cron check-ins - #3200
Merged
Merged
Conversation
solnic
force-pushed
the
feat/good-job-cron-check-ins
branch
2 times, most recently
from
November 11, 2026 13:40
6231a01 to
cc72ec7
Compare
solnic
force-pushed
the
feat/good-job-cron-check-ins
branch
3 times, most recently
from
November 12, 2026 14:25
4bf324f to
61b4561
Compare
solnic
marked this pull request as ready for review
November 12, 2026 15:17
dingsdax
approved these changes
Nov 16, 2026
Sends check-ins for GoodJob cron entries when the :good_job_cron patch is enabled, using the cron key as the slug and the entry's schedule as the monitor config. Keys can be skipped with config.rails.good_job_exclude_cron_jobs. Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Claude <noreply@anthropic.com>
Keys that map to the same slug, like long keys cut at 50 characters, would share one monitor with two schedules. Skip all of them and warn, and log at debug level when a schedule can't be expressed. Co-Authored-By: Claude <noreply@anthropic.com>
GoodJob sets its cron key only while an entry enqueues and clears it while jobs run, so a job a cron job enqueues inline isn't tagged. Zoneless schedules use the app's time zone rather than whatever zone the enqueue runs under.
Excluded entries, unconvertible or proc schedules, and jobs that call sentry_monitor_check_ins don't send check-ins for the slug, so they shouldn't stop another entry from being monitored. The schedule check runs first so unmonitorable entries don't get the rename warning.
FugitSchedule.from_cron only returns a config with both a crontab and a time zone.
Other jobs enqueued during a cron enqueue, a failure while building the monitor, callable classes, unconfigured MonitorCheckIns, and a nil exclude list.
solnic
force-pushed
the
feat/good-job-cron-check-ins
branch
from
November 16, 2026 09:11
61b4561 to
64a9af1
Compare
solnic
force-pushed
the
feat/good-job-cron-check-ins
branch
from
November 16, 2026 11:36
16fb4f7 to
68998b4
Compare
solnic
force-pushed
the
feat/good-job-cron-check-ins
branch
from
November 16, 2026 12:39
7323727 to
b014966
Compare
solnic
force-pushed
the
feat/good-job-cron-check-ins
branch
from
November 16, 2026 14:47
ea76dcf to
4e07d34
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 4e07d34. Configure here.
|
Funny or not, Claude gets attribution, amkisko does not. :D What a time or has it been always like that. |
This was referenced Nov 18, 2026
3 tasks done
4 of 5 tasks
dingsdax
added a commit
to getsentry/sentry-changelog
that referenced
this pull request
Nov 18, 2026
Adds a changelog post for [sentry-ruby 7.3.0](https://github.com/getsentry/sentry-ruby/releases/tag/7.3.0), so Ruby users hear about the release's new features in the changelog and in Sentry's "What's New" panel (scoped to Ruby, Rails, and Rack orgs) and not only in the GitHub release notes. The post is framed around background work that fails quietly, and each section leads with the problem it solves: - **Know when a GoodJob cron job fails or never runs**: `config.enabled_patches << :good_job_cron` puts every GoodJob cron entry under Crons monitoring (getsentry/sentry-ruby#3200) - **See which feature flags were on when an error happened**: `Sentry.add_feature_flag` attaches flag evaluations to errors and spans (getsentry/sentry-ruby#3108) - **Spot jobs piling up in the queue**: ActiveJob, Sidekiq, and Resque jobs report queue wait time and payload size for the Queues dashboard (getsentry/sentry-ruby#3133) It closes with `Sentry.logger` block support (getsentry/sentry-ruby#3178), then links the full release notes. The new job extensions API (getsentry/sentry-ruby#3129) is left out because it only matters to people who maintain job backends. Nothing breaks. Open decisions: - The entry is `published: false`, so merging only creates it. To go live, set `published: true` before merge or publish it from the admin UI. - `author` is left unset because I couldn't confirm which email belongs to an existing changelog user. Add one if you want the post attributed. <!-- junior-request-attribution:start --> via @dingsdax. <!-- junior-request-attribution:end --> <!-- junior-session-footer:start --> <!-- junior-conversation-id:local%3Aweb%3Ab5614f77a180622dc700158a --> -- [View Session](https://junior-prod.sentry.dev/conversations/local%3Aweb%3Ab5614f77a180622dc700158a) [[Sentry]](https://sentry.sentry.io/explore/conversations/local%3Aweb%3Ab5614f77a180622dc700158a/?project=4510944073809921) <!-- junior-session-footer:end --> --------- Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com> Co-authored-by: johdax <114897+dingsdax@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

This branch is built on #3147.