The message flow works perfectly for 5 mins. After that it throws the error "Timeout Time cannot be in the past".
Strangely the StartTime is always taking the value of the time at deployment time and hence after 5 mins (which I guess is internal to the broker), it throws the error "Timeout Time cannot be in the past".
Can you please help me with a solution such that this error does not occur.
"The start time can be calculated by adding an interval to the current time. If a delay occurs between the node that calculates the start time and the TimeoutControl node, the start time in the message will have passed by the time it reaches the TimeoutControl node. If the start time is more than approximately five minutes in the past, a warning is issued and the TimeoutControl node rejects the timeout request. If the start time is less than five minutes in the past, the node processes the request as if it were immediate. Therefore, ensure that the start time in the timeout request message is now or a time in the future."
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum