Schedule periods

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Schedule Periods

    The schedule periods for surveys include Only Once, No Limit, Daily, Weekly, Monthly, and Yearly, with No Limit set as the default. When a schedule period is selected (other than Only Once or No Limit), a scheduled job is created to manage survey instances.

    Show full answer Show less

    Key Features

    • Single Survey Instance: Users can only take one survey instance per schedule period unless they have an incomplete instance.
    • Automatic Instance Generation: A new survey instance is generated for users at the start of each schedule period, provided previous instances are complete.
    • Expiration Management: The expiration date field on survey instances controls when users can receive new surveys, automatically set based on the selected schedule period.
    • Dynamic Updates: Changing the schedule period automatically updates the scheduled job, but users with existing instances must wait for them to expire before receiving new ones.

    Key Outcomes

    Customers can expect streamlined survey distribution based on defined schedule periods, ensuring users receive timely and relevant survey requests while maintaining control over survey instance management. For scenarios involving trigger conditions, it is important to set the schedule period to No Limit to ensure proper functioning.

    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.

    For example, if you set the schedule period to Monthly and someone attempts to send survey invitations 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.

    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.

    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.

    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.

    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.

    Note:
    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.