Incomprehensible exception

Hello everyone. I am getting a strange exception in my model which otherwise works fine. But I cannot have this pop-up in a presentation. Kindly help me understand it:

time: 1433.640145 exception: Exception Caught in dispatchtasksequence(fsnode* tasksequence, fsnode* dispatcher DEFAULTNULL)
time: 1433.640145 exception: Exception Caught in ObjectFunction080__project_exec_commandlist_dispat chtasksequence_node object: MAIN:/project/exec/commandlist/dispatchtasksequence/node class: MAIN:/project/exec/commandlist/dispatchtasksequence/node

You may pass in a invalid ts, dispatcher or te. You can search where you call this function. Put a debug point there, run the model and see what happens for this function.

Thats the whole problem. Where is the invalid TS being passed ?

Hello Arjun,

I think, I have read the following advices before, but I can't find them anymore.
Make your model repeatable. The thread of Cliff King will help you.
Run the simulation to get the exception.
Set a stop time previous to the exception time.
Run the simulation again.
Analyze your model.
Look in the events in the main tree.
Step to the next event in the model run dashboard.

If you use customized tasksequences, insert a tag task with an information of the object dispatching the tasksequence and creationtime. But beware of dependencies to tasksequences which use the number of tasks or a special order.
Edit:
If you know the taskexecuter throwing the exception, you can insert a tag task to every received tasksequence with the information of the receiving time in that taskexecuter. Look for the object at the next run which holds that tasksequence previous to the taskexecuter. If it isn't the dispatcher of the tasksequence, use the previous method again and insert a tag task to identify the receiving time. A place to insert a task is the Place To function of taskexecuters or dispatchers.


Jörg

You can find exceptions easier using the Event Log (Debug > Event Log). It logs exceptions as an entry in the table. The entry immediately above the exception entry is the code where the exception happened.