State Machine - init state - infinite loop

Hi folks,

I just have a pretty stange problem: I set up my state machine for a process as I did before for many others too.

But now, somehow, the robot is perfoming an infinite loop - without stopping. I really have checked if there could be a difference to the other processes (which are working fine). But there is no one.

Hence, my question: Why could there be an infinite loop in the initial state machine? Do you have any ideas? Please help :slight_smile:

Best regards and thousands thanks

It’s hard to say without looking at your state machine, but if it is set up to do retries of the Init state and it never hits the MaxRetryNumber then it could keep going. I would also check the conditions in your pathways to each state to make sure it’s traveling correctly. Also, check your Output tab while it is running and see if it’s logging anything; it is helpful if errors and retry attempts are outputted there so you know what’s going on.


SetTransactionStatus.xaml failed: The values provided for the root activity’s arguments did not satisfy the root activity’s requirements:
‘SetTransactionStatus’: Expected an input parameter value of type ‘UiPath.Core.QueueItem’ for parameter named ‘in_TransactionItem’.
Parameter name: rootArgumentValues at Source: UiPath.Core.Activities

Hi Clayton,

Many thanks for your quick reply.

I just added the error/info message I get. Does this help?

Best regards

The strange thing here is, that the SetTransactionStatus.xaml is just like the other ones from my other processes. So I can’t find any error there…

You variable and argument for TransactionItem should be all QueueItem or the type you have defined.
You can verify once inside your SetTransactionStatus.

Yeah, if there is an error happening while trying to use the in_TransactionItem argument, it is supposed to exit to the Closure State. There must be an issue with your condition on the transition/pathway that goes from Init to Close (or whatever the state name is lol)

If the condition says SystemError isNot Nothing then ensure that SystemError is assigned exception in the Catch inside the Init State, otherwise it will never exit out.

To resolve the actual error see nadim’s suggestion :smiley:

Oh somehow, my Thank You Guys message didn’t come through.

Thank you guys!!! It’s working now :slight_smile:


This topic was automatically closed after 2 hours. New replies are no longer allowed.