Auto-lock failure notification

This notification is sent after five unsuccessful attempts to automatically lock a form question.

If you receive the Auto-lock failure notification, take one of the following actions based on your study’s setup:

If your study doesn’t include auto-lock predefined rules, you can ignore any Auto-lock failure notifications you receive in your inbox.
If your study includes auto-lock predefined rules, but not for the visit and event mentioned in the Auto-lock failure notification, you can ignore the notification.
If your study includes auto-lock predefined rules for the visit and event mentioned in the notification, you need to manually lock the relevant questions. Locate the visit that is referenced in the Auto-lock failure notification, identify which questions have the auto-lock rule configured, and lock them in your study. For step-by-step guidelines on how to manually lock data, see Lock a form or visit.

Tip:

Having trouble finding the question to lock? Run the Study Design report and check the Action Rules column. Any question with an Auto-lock rule will indicate that in this column.

Permissions required to receive the notification

Sponsor users with the Lock Subject Data permissions and assigned to the impacted sites will receive this notification.

Field descriptions

This notification also contains an introductory statement indicating that the rule for automatic data locking, for one or more questions, triggered by a visit has failed. It also prompts the user to lock the questions manually and contact support for assistance.

Field	Description
Title	Title of the notification, for example, Auto-Lock failed.
Study Name	Study's ID again, as specified by the global study creator when they created the study.
Study Mode	Study mode associated with this notification. Displayed values can be: Production Testing Training
Site Name	Name of the site as specified by a site manager when they created the site.
Subject Number	Number of the subject.
Visits	Name of the visit where the locking was scheduled to trigger.

Parent topic: Rule notifications