Troubleshooting Approval Process Issues

This section lists some of the most common reasons that errors can occur in the Approval process.

Locking failure due to Invalid Data error

You may encounter an"Invalid Data" error when you try to lock an entity. If you are using the Approval card to perform the lock action, you can click the error message "Invalid Data" to view the error detail in the form. This error can occur for the following reasons:

  • Prior period of this target entity and / or its descendants is not locked.

  • Any of the previous periods of the current year of this target entity and/or its descendants is not locked.

See Locking and Unlocking Entities.

Unlocking failure due to Invalid Data error

You may encounter an "Invalid Data" error when you try to unlock an entity. If you are using the Approval card to perform the unlock action, you can click the error message "Invalid Data" to view the error detail in the form. This error can occur for the following reason:

Any of the future periods of the current year of this target entity and/or its descendants is locked.

See Locking and Unlocking Entities.

Intermittent failure during the Approval process

While performing Approval actions such as Lock, Unlock, Promote, Approve, or other actions, sometimes the action may fail.

To work around this known issue before a fix is available, in the Approval card after the action is taken, do not refresh the page continuously. You may need to wait for some time until the action is completed and then refresh the page.

Start action failure due to Failed: Ambiguous Automatic User error

Starting an entity for the Approval process is an action performed by the Administrator. This process will assign the owner for the entity and place it in the correct location of the promotional path.

However, if there is no specific owner assigned to this entity, or if there is no owner assigned at the root level of the Approval Unit Hierarchy, there will be no owner assigned to this target entity as part of the Start process.

To avoid the potential error of not being able to assign an owner to the entity, be sure to assign at least one owner at the root level entity of the Approval Unit Hierarchy. As long as there’s at least one owner assigned at the root level entity, any of the descendants will be able to inherit the owner assignment from the root if there’s no specific owner assigned to this entity.

See Assigning Approval Unit Owners and Reviewers.