---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Schedule periods

# Schedule periods {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

The available schedule periods are Only Once, No Limit, Daily, Weekly,
Monthly, and Yearly.  
The default schedule period is No Limit. When you set the schedule period to anything except Only Once or No Limit, the system creates a corresponding scheduled job. The scheduled job performs the following actions.

* Ensures that a user can take one survey instance of the same survey per schedule period.
* Generates a new survey instance for each survey user at the beginning of the new schedule period, as long as the survey user does not have an incomplete instance of that survey. A survey instance is incomplete if the state is not Complete.
{#c_SchedulePeriods__ul_c5c_kp4_1r}

For example, if you set the schedule period to Monthly and someone attempts to
[send survey
invitations](https://servicenow-prod.fluidtopics.net/3KIUjCH5a6IDITDLwX3jEQ "You can send survey invitations using the Assign Survey or Send Invitations buttons on the Survey Definition form.") twice in the same day, the system generates survey instances for the survey
users the first time only. At the beginning of the next schedule period, the system generates
another survey instance for each survey user who completed the previous one.{#c_SchedulePeriods__p_ymb_nfg_h1c}

Schedule periods are enforced by the Expiration date field on the survey
instance. As long as the survey instance expiration date has not passed, the assigned user cannot
receive a new survey instance. When the system generates a survey instance and the schedule
period is anything except No Limit, the Expiration date field is automatically set to the appropriate date. For example, if the
schedule period is Weekly, the expiration date is a week after the survey
instance is generated.{#c_SchedulePeriods__p_zmb_nfg_h1c}

If you change the schedule period, the scheduled job updates automatically to the correct
schedule. However, users who have survey instances for the survey cannot receive new survey
instances until their existing survey instances expire, regardless of the new schedule period.{#c_SchedulePeriods__p_anb_nfg_h1c}  
Consider the following example: Sal Pindell receives a survey instance when the schedule period is Weekly. The next day, a survey administrator changes the schedule period to No Limit. Sal cannot receive another survey instance until one of the following actions occurs.

* Seven days pass from the time Sal's survey instance was generated.
* A survey administrator deletes Sal's survey instance.
{#c_SchedulePeriods__ul_i3n_5p4_1r}

After one of these actions occurs, Sal can receive a new survey instance anytime, as long as he
has no incomplete instances of the survey.{#c_SchedulePeriods__p_cnb_nfg_h1c}  
Hinweis:  
If you use a trigger condition for a survey, ensure the schedule period is set to No Limit. Trigger conditions use a different method to regulate how often users can receive survey instances.
**Zugehörige Konzepte**   

* [Survey trigger conditions](https://servicenow-prod.fluidtopics.net/dtF46gcd8iGVa~2r1Fjriw "Trigger conditions specify when to send a particular survey and the persons to send it to.")  
**Zugehörige Tasks**   

* [Publish a survey](https://servicenow-prod.fluidtopics.net/MXVckIM4qQsYVKnnVuodag "You must publish a survey to enable people to receive and complete survey instances.")