> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://tester.army/docs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://tester.army/_mcp/server.

# Production Monitoring

Production Monitoring execute tests at a fixed time, on repeat. Use them for nightly smoke checks, regression catching, or monitoring key flows outside of PR activity.

Disabled tests in the selected group are skipped. You can still run a disabled test manually from its test page.

## Set up Production Monitoring

1. Open **Project → Tests** tab.
2. Click the **Triggers** button.
3. Click **New Production Monitoring**.
4. Set:
   * **Frequency**: Hourly, Daily, Weekly, or Custom cron
   * **Time and timezone**
   * **Day of week** (weekly only)
   * **Cron expression** (custom only)
   * **Test group** to execute - each production monitor runs a test group you've already [created](/run/groups)
5. Save.

![Production Monitoring configuration](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/testerarmy-subpath.docs.buildwithfern.com/29f2bcf48de3427ef0affc99281255b4093d037e49b8875dc082ec3903da7e0e/docs/assets/docs/production-monitoring.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260817%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260817T151642Z&X-Amz-Expires=604800&X-Amz-Signature=1632e3b4a2d1e602cf779885ba3792dcbfa92e4c2e774b306f7207e740369bfb&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

## Custom cron schedules

Pick **Custom cron** when the presets don't cover the cadence you need, for example weekdays only (`0 8 * * 1-5`) or every 30 minutes (`*/30 * * * *`).

The expression uses standard 5-field cron syntax - `minute hour day-of-month month day-of-week` - and runs in your browser's timezone. Seconds are not supported.

Steps are evaluated inside each field's own range rather than as rolling intervals, so `0 9 */14 * *` runs on the 1st, 15th and 29th of every month rather than strictly every 14 days.

## Failure notifications

If any test in a monitored run fails, TesterArmy sends a failure summary to connected chat providers such as [Slack](/integrations/slack) or [Discord](/integrations/discord). If no chat provider delivers, you'll receive an email notification so you can act on it right away.

## Tips

Keep each monitor focused. A monitor that tries to test login, billing, and settings in one go is harder to act on when it fails. Split those into separate groups instead.