question

Instead of using the gettasksequence() command like you are in the logic, I would use the gettasksequence() command like this:

int condition = !objectexists(gettasksequence(current.centerObjects[2], 0));

Using a 0 as the second parameter will cause gettasksequence to return the current active task sequence. The !objectexists() then will return true if the Task Executer does not have an active task sequence (it is at the home location not doing anything).

However, there is a problem doing it this way because there is a delay before the flowitem gets to the Exit Transfer where the task sequence is created and sent to the Task Executer. That means it's possible to for another box to trigger the Decision Point logic when the Task Executer does not have an active task sequence yet.

My suggestion would be to either use Process Flow and lists to handle checking when the Task Executer is being used. Or you could simply set a label on the Task Executer when you know it will be given a task sequence, then check that label as part of your condition. Then set the label to a different value as part of the travel task back to the home location. You can edit the OnResourceAvailable trigger and use the TASKTYPE_SETNODENUM task to change a label value or use the TASKTYPE_SENDMESSAGE task and have the Task Executer send a message to itself and change the label value in the OnMessage trigger.