# Guides

> How to find out when a Laravel job fails, a scheduled task doesn't run or your app goes down, and how to debug production errors with Claude Code.

- [Debug Laravel production errors with Claude Code](/guides/debug-laravel-production-errors-with-claude-code/): Connect Claude Code to your error tracker over MCP, then let it find new errors, read the stack trace, open your code and propose a fix you review.
- [How to know when your app is down](/guides/know-when-your-app-is-down/): Five things take a web app offline: the host, an expired SSL certificate, a lapsed domain, changed DNS and broken links. How to spot each one yourself.
- [Why Laravel queued jobs fail, and how to find out](/guides/laravel-failed-jobs/): A Laravel job fails when it throws on its last attempt, times out or runs out of attempts. It lands in failed_jobs and nobody is told unless you add a hook.
- [Monitor the Laravel scheduler, and why tasks silently don't run](/guides/monitor-laravel-scheduler/): Laravel's scheduler runs only when cron calls schedule:run each minute. Missing cron, stuck locks and timezones skip tasks silently; a heartbeat catches it.
- [Telescope and Pulse in production, and when to use a hosted tool](/guides/telescope-pulse-in-production/): Telescope records single requests, Pulse aggregates. Both run in production with a gate, filters and pruning, but neither alerts you when something breaks.