Planning Engine locking mechanism
The locking mechanism is used to prevent concurrent activities for a planning engine to
ensure data consistency. The limitations are applied at the planning engine level and are
applicable to all users of a Planning Engine.
The locking mechanism can be used to prevent:
- User update and processing actions from running concurrently
- Update actions being performed when a prior update or read action is executed
- Read actions being performed when an update action is executed
These recommendations must be followed to reduce the impact of the locking mechanism on users:
- Import and long running workflows must be automated and run outside normal daily activities.
- Imports, Exports and workflows must not be executed concurrently.