Overview
This page will be a guide to troubleshoot a misconfigured automatic population of an user-picker field.
Symptoms
When loading the issue a Warning appears that says 'The automatic population of an user-picker field has been stopped because it is misconfigured.
The app stop (for 5 minutes) to perform the automatic population of an user picker custom field that has been configured on a requested Approval relating the current issue.
The History tab shows that the user picker custom field changed its value ten times in the last five minutes.
Cause
When populating an user picker custom field that has been configured on a requested Approval relating the current issue, the app checks for changes on the values of this custom field during the last five minutes.
Case of the user picker custom field value changed more then 10 times, the app avoid to update the custom field in order to prevent a possible loop.
The cause of the problem can relates to one of one of the following reasons
- any third part apps run any script that populate the same user picker with a different values
- two or more Approval configuration address the same user picker using expressions that returns a different list of users
How to troubleshoot the error
Navigate on the Approvals configuration to populate the User Picker Custom Field.
Example
- Identify requested Approvals
- Review Approvals Configurations
- Fix the inconsistency so to avoid to populate the same user picker with different values.
Example: Change the userpicker associated to the User Picker (multiple users)2
In this section
| Table of Contents |
|---|
Need support?
We would love to help.
Button Hyperlink
| Info | ||
|---|---|---|
| ||
|