# Notification settings

> Digest frequency, time and timezone, and channel tests.

Admins and owners set these per project under **Notifications** in the project.

## Digest frequency

Choose how often digests are sent: every hour, 3 hours, 6 hours, 12 hours or 24 hours. Your plan sets the shortest interval allowed; asking for less returns [`plan-limit-reached`](https://docs.dlogify.com/errors/plan-limit-reached.md) with `limit: "min_digest_minutes"`.

- **Every 24 hours** sends at the time you choose.
- Shorter intervals are counted from midnight in the project's timezone: every 6 hours means 00:00, 06:00, 12:00 and 18:00.

Each digest covers the time since the previous one, so periods never overlap or leave gaps. A change takes effect within a minute.

## Timezone

Digests follow the project's timezone, an IANA name such as `Europe/Madrid` or `America/New_York` (default `UTC`). Daylight saving time is handled: once a year, when clocks go back, one period is longer than usual.

## Empty digests

When a period has no tickets, no INFO activity and no newly failing channel, nothing is sent.

## Test a channel

Choose **Send test** on a channel, or call [`POST /v1/channels/{channel_id}/test`](https://docs.dlogify.com/api/channels/testChannel.md), to send one test notification right away. A webhook receives a body with `"type": "test"` (see [Test body](https://docs.dlogify.com/webhooks.md#test-body)); an email has the subject `[Logify] Test notification for <project>`. You can test a channel once a minute.

## Channel health

A channel is marked as failing after three deliveries in a row fail for good. It keeps receiving deliveries; the next delivered ticket, digest or test marks it healthy again. A failed test does not count toward failing.

Source: https://docs.dlogify.com/notifications/settings
