yesterday I discovered that AGV doesn't change the state when it receives a new mission, but it can't start it. I reproduced the issue in the model agv-blocked.fsm.
The task executer 3 receives a travel task which can't start because the task executer 1 has already allocated the area. Correctly the TE3 doesn't go, but its state is set to "travel_empty" instead of "blocked". Is it a bug or is there an error in my implementation?
After some test I noted that the state_blocked is set only when the AGV reaches a control point and can't allocate the next one or when it must stop to due to accumulation rule. Can someone confirm it?
