Guided Path Deadlock Exception
Thrown when transporters have formed a circular wait and the run cannot continue.
This is a domain outcome, not a defect. The model is valid and the answer is that this configuration deadlocks, which is often the finding a study is after. A run that reaches this state is aborted rather than repaired, because any automatic repair would silently change the system being modeled.
Detection runs when a transporter becomes blocked, which is the only moment at which a cycle can form, so the exception is raised at the instant the deadlock comes into existence rather than after the run has quietly stopped advancing.
A user sweeping a parameter region that contains deadlock should catch this around the replication and record the design point as infeasible.
Parameters
the participants in the cycle and the time it formed