Skip to main content

Device State Modified in Parallel

Platform: Process Simulate

Two operations that may run at the same time both change the state of the same robot, joint, or device. Because the order is not guaranteed, this could modify the affected geometry in parallel and cause race conditions, so Resolver does not allow it and blocks the export.

Dialog shown in Resolver​

Unexpected error while exporting project: Conflict detected: robot {robotName} state modified in parallelParent Operation: {operationA}Via: {pathA}Parent Operation: {operationB}Via: {pathB} This may result in modifying the affected geometry in parallel which may lead to race conditions and it is not allowed.

What you can do in this dialog​

  • Can you continue export? No
  • Buttons in the popup: OK
  • What happens next: The export does not continue until the conflicting operations are corrected.
  • Next step: How to fix it

Impact if you continue​

Export cannot complete while two parallel operations modify the state of the same robot, joint, or device. Allowing it would let the device be changed in an undefined order, producing inconsistent geometry.

How to fix it​

  1. Open the two Parent Operations named in the dialog and review how each reaches the reported robot or device.
  2. Restructure the sequence so only one operation modifies that device's state at a time — for example, add an ordering dependency between the operations, or move the conflicting state change so the operations no longer run in parallel.
  3. Save the study and re-run export.