Description

dingsdax

opened on Oct 21, 2026

Issue body actions

No description provided.

Activity

1. linear-code commented on Oct 21, 2026

   

   linear-codeBot

   on Oct 21, 2026 – with Linear Code

   More actions

   PY-3033
2. dingsdax

   added

   Checks

   Crons

   Feature

   PythonSDKSDK

   on Oct 21, 2026
3. Gkhalifa commented on Oct 25, 2026

   

   Gkhalifa

   on Oct 25, 2026

   More actions

   Hi, I’d like to take this one if it’s open to an outside contribution and nobody’s on it.

   There’s no description on the issue, so I’d rather check my reading than guess. My plan would be to model it on the existing Celery Beat integration in sentry_sdk/integrations/celery/beat.py, since that’s already doing the scheduler-to-Crons wiring, and to reuse capture_checkin and the helpers in sentry_sdk/crons rather than adding anything new there. IntervalTrigger maps onto _get_interval_schedule fairly directly, and CronTrigger would need a crontab string assembled from its fields.

   Two questions before I start. Is this something you’d want from outside, given it’s tracked in Linear? And do you want APScheduler 3.x only, or 3 and 4? The APIs differ enough that supporting both would change the shape of the integration.
4. getsantry

   added

   Waiting for: Product Owner

   on Oct 25, 2026
5. getsantry

   added this to GitHub Issues with 👀 3on Oct 25, 2026
6. getsantry

   moved this to Waiting for: Product Owner in GitHub Issues with 👀 3on Oct 25, 2026
7. dingsdax commented on Nov 5, 2026

   

   dingsdax

   on Nov 5, 2026 – with Linear Code

   ContributorAuthor

   More actions

   thx for the offer, really appreciate it, but we already tackled this internally
8. Gkhalifa commented on Nov 5, 2026

   

   Gkhalifa

   on Nov 5, 2026

   More actions

   7. thx for the offer, really appreciate it, but we already tackled this internally

   appreciate you letting me know, thanks.

Issue actions