iLert Documentation
WebsiteAPI ReferenceLoginFree Trial
Search…
iLert Documentation
Getting Started
Introduction to iLert
On-call schedules
My on-call shifts
Recurring schedules
Static schedules
User roles and permissions
Team-based organisation
Stakeholder engagement
iLert domains, ips, emails & phone numbers
FAQ
Call Routing
Getting started with call routing
Routing calls based on support hours
Voicemail only mode
Managing call routing alerts
Adding webhooks and outbound chat messages
Single Sign On
Setting up SSO with GSuite
Setting up SSO with Microsoft Azure Active Directory
Setting up SSO with Okta
Setting up SSO with Auth0
Auto provisioning users & teams
Uptime & Heartbeat Monitors
Uptime Monitoring
Heartbeat Monitoring
REST API
iLert REST API
API Version History
Rate Limiting
Client Libraries
Terraform
API Samples
Integrations
Amazon CloudWatch Integration
Azure Alerts Integration
AppDynamics Integration
AWS Budget Integration
AWS GuardDuty Integration
AWS Lambda Integration
AWS Personal Health Dashboard Integration
Amazon SNS Integration
Amazon EventBridge Integration
Autotask Integration
Azure Function Integration
Auvik Integration
Cisco Webex
Cloudflare Integration
Connectwise Manage Integration
Cortex XSOAR (formerly Demisto) Integration
Checkmk Integration
Datadog Integration
Discord Integration
DingTalk Integration
Dynatrace Integration
Email Integration
Email Outbound Integration
GitHub Integration
Google Cloud Function Integration
Google Cloud Monitoring (formerly Stackdriver) Integration
Grafana Integration
Icinga Integration
Instana Integration
IXON Cloud Integration
Kapacitor Integration
Kentix AlarmManager
Kubernetes Integration
HashiCorp Consul
Jira Integration
JumpCloud Integration
Mattermost Integration
Microsoft Teams Integration
MXToolBox Integration
N-central Integration
Nagios Integration
New Relic Integration
Pingdom Integration
Prometheus Integration
PRTG Network Monitor Integration
Push Notifications
Raygun Integration
Salesforce Integration
Search Guard Integration
Sematext Integration
Sensu Integration
Sentry Integration
Server Density
ServiceNow Integration
SignalFx Integration
Single Sign-On Setup
Slack Integration
SMS Integration
SolarWinds Integration
Splunk Integration
StatusCake Integration
StatusHub Integration
StatusPage Integration
Sumologic Integration
Sysdig Integration
TOPdesk Integration
Terraform Cloud / Terraform Enterprise
UptimeRobot Integration
Webhook Integration
X-Pack Alerting (Elasticsearch Watcher) Integration
Zabbix Integration
Zapier Integration
Zendesk Integration
Zammad Integration
Zoom Integration
Contact us
iLert Release Notes
iLert Mobile Release Notes
Powered By GitBook
Recurring schedules
Recurring schedules are a flexible way to create complex recurring schedules with minimal effort.

Create a recurruing schedule

To create a recurring schedule, navigate to On-call schedules, click on Create new on-call schedule and chose Create recurring schedule as the schedule type.

Step 1: Add users

Add the users from the dropdown menu. Users will rotate in the order they are listed. You can change the order via drag and drop and remove a user by clicking on the x icon.

Step 2: Set on-call rotation

The on-call rotation determines when a shift should rotate from one user to the next user. Chose between daily and weekly rotations. For example, if you want your users to rotate every week, enter 1 week, if you want them to rotate bi-weekly, enter 2 weeks, and so on.
In the Starts on field, chose the start time of your schedule. Note that the start time will also determine the time when a user's on-call duty is handed over to the next user in the rotation.

Step 3: Set on-call coverage (optional)

By default, the on-call coverage is 24 hours a day, 7 days a week, i.e. users are on-call all the time. If you want to restrict times on-call, e.g. to outside working hours only, you can do so in this step.
Restricting your on-call coverage will result in gaps in your schedule, where no one is on call. If an alert occurs during a time with no coverage in your schedule, then the alert will be escalated immediately to the next escalation level, without waiting for the escalation timeout. If no one is on-call on the entire escalation policy, no one will be notified.
Previous
My on-call shifts
Next
Static schedules
Last modified 19d ago
Copy link
Contents
Create a recurruing schedule
Step 1: Add users
Step 2: Set on-call rotation
Step 3: Set on-call coverage (optional)