• Periodic – The agent runs the activity and then sleeps for the number of seconds entered in the Interval column.
• Recurring – The agent runs the activity based on a specified calendar schedule (for example, every Monday at 5:00 P.M.).
• Startup – The agent runs the activity once at startup based on a specified parameter.

This value overrides the Pattern specified in the corresponding agents rule (from which this agent schedule was generated).

When the master agent initially creates an agent schedule instance, the value of this option is copied from the corresponding agent rule. If the agent rule's Enable this agent option is enabled, the corresponding agent schedule instance or instances are enabled and processing begins.

If agent processing produces a Java exception, in most cases, the exception details are added to the Pega log and the system clears this option, disabling the agent (on one node). You can restart the agent on this node by updating the Agent Schedule data instance or from Admin Studio.