Cyclical Dependency in Operations
Platform: Process Simulate
The operations depend on each other in a cycle, so Resolver cannot determine a valid order to execute them. The export is blocked until the cycle is removed. This usually points to an unexpected modeling structure; if you cannot identify the cause, contact support with the study and logs.
Dialog shown in Resolver
The following operations are forming a cyclical dependency: Operation: {operationName}, Parent: {parentName}
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 cyclical dependency is removed.
- Next step: How to fix it
Impact if you continue
Export cannot complete while operations form a cycle. Resolver has no valid execution order to build from a circular dependency.
How to fix it
- Open the operations listed in the dialog and review how each one depends on the others (parent operation and any ordering links).
- Break the cycle by removing or redirecting the dependency that closes the loop, so the operations form a one-directional order.
- Save the study and re-run export.
- If the operations look correct and the cycle is unexpected, contact support and attach the study and exported logs.