To send an accountability event on a recurring basis without the need to manually send the event each time, set a recurrence in the accountability template.

Accountability templates that are configured to recur and have a next occurrence date set must have affected users and devices selected for the scheduled accountability event to publish. If affected users or devices are removed from the accountability template, the scheduled accountability event does not start and has the recurrence setting removed. This prevents accountability events from being published without affected users or targeted devices.

Recurring accountability templates retain the Status attribute values that were configured when the template was last saved. BlackBerry AtHoc blocks edits to Status attribute values while the attribute remains assigned to a recurring template. To make changes before the next scheduled occurrence, remove the Status attribute from the template, update the attribute values, and then reapply it to the template.