getsentry / getsentry/sentry

Crons: "No issues relating to this cron" when I see failed checkins with linked errors

Open
#93,086 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 10m
Merged PRs (30d)
635

Description

As seen on in this cron job: https://sentry.sentry.io/issues/alerts/rules/crons/android-symbol-collector-runner/device-farm-symbol-collection-saturday/details/?project=4509420348964864&statsPeriod=24h

There's an empty list with:

> No issues relating to this cron monitor have been found.

But right below, I see 2 failures, with links to Sentry issues:

![Image](https://github.com/user-attachments/assets/d15325e5-3847-45c3-8b77-54934d55bb79)

Contributor guide

Open the contributing guide

Research direction

Open the linked cron monitor details page and compare the empty related-issues list with the two failed check-ins and their linked Sentry issues. Trace the cron monitor details and issue-linking entry points, then verify that failures with linked errors appear in the list and that the empty state is shown only when none are related.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
observability
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.