> For the complete documentation index, see [llms.txt](https://docs.xenoraa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xenoraa.com/xenoraa-changelog-and-architecture/v10.0.4-sentry-cron-fix.md).

# v10.0.4 — Sentry Cron Fix

## v10.0.4 — Sentry Cron Fix

### v10.0.4 — Fix: Sentry Cron Check-in for xenoraa-notification-reminders

**Released:** 2026-07-10 | **Category:** Bug Fix | **Commit:** [`bb13b6c`](https://github.com/goesscay/xenoraa/commit/bb13b6c) | **Fixes:** [XENORAA-2](https://esscay.sentry.io/issues/XENORAA-2)

#### Root Cause

`sentryMonitor()` sends check-ins via `->before()` and `->onSuccess()` callbacks that run in the **parent** `schedule:run` process. The parent exits immediately after spawning the command as a subprocess, abandoning the async Sentry HTTP curl request mid-flight. No check-in ever reached Sentry, causing 13 "missed check-in" alerts over 6 hours.

#### Fix

Moved check-ins directly inside `handle()` using `\Sentry\captureCheckIn()` which is **synchronous** and runs in the actual command process.

#### Files Changed

**`app/Console/Commands/SendNotificationReminders.php`**

* Added `captureCheckIn(inProgress)` at the start of `handle()`
* Added `captureCheckIn(ok)` after successful execution
* Added `captureCheckIn(error)` in the catch block if an exception is thrown
* `MonitorConfig`: `schedule=0,30 * * * *`, `checkinMargin=5min`, `maxRuntime=10min`, `timezone=UTC`

**`app/Console/Kernel.php`**

* Removed `->sentryMonitor('xenoraa-notification-reminders')` — check-ins are now handled internally by the command itself.

#### Outcome

* Sentry Issue **XENORAA-2** resolved (was: 13 missed check-in occurrences over 6 hours)
* Monitor `xenoraa-notification-reminders` will now show `ok` status after each successful run

#### Important Note

`trial-reminders` and `xena-daily-snapshot` still use `sentryMonitor()` in Kernel.php because they run **daily** (not every 30 minutes) — the parent process has enough time to flush the HTTP request. If they also show missed check-ins, apply the same `captureCheckIn()` pattern inside their `handle()` methods.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.xenoraa.com/xenoraa-changelog-and-architecture/v10.0.4-sentry-cron-fix.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.