Deadline determination failed

[Former Member]

Hello,

in my wf scenario I have one task with deadline monitoring - requested end. Deadline time is calculated so i use Expression as reference time. But SOMETIMES the wf finish in status error with these messages:

Error when processing node '0000000386' (ParForEach index 000000)

Work item 000000941341: Object FLOWITEM method EXECUTE cannot be executed

Deadline determination failed

Error during result processing of work item 000000958108

Error when processing node '0000000386' (ParForEach index 000000)

Error when creating a component of type 'Krok'

Error when creating a work item

Work item cannot be completed -> end condition is 'incorrect'

When i tried to restart this wf in swpr i get different error:

Unable to start subflow (ID: 000000941341, node: 0000000001)

Work item started following error (new status STARTED)

The variable in container contains right value for reference time.

Any ideas?

Thx,

JJ

[martin_nooteboom]

Hi Jiri,

What kind of task is this where you have the deadline? As far as I can tell the error is not related to the deadline, but thrown because the workitem couldn't be ended correctly. Does this task have an end condition defined? And what is the component Krok?

Regards,

Martin

[Former Member]

Hi Martin,

thank you for your answer,

The task which is not created is a dialog task with latest end and the condition for finish of processing:

&_WI_RESULT& = OK or

&_WI_RESULT& = RETURN

Task is based on some method of BO which returns value(wi_result).

'Krok' means 'Step'

JJ

[martin_nooteboom]

Hi Jiri,

Is the outcome created by the condition active? Otherwise this will go in error. Maybe there is another outcome which is not active?

Regards,

Martin

[Former Member]

But the condition contains the result of the BOR method, so it is not true at the time when the task is created.

[martin_nooteboom]

So it goes into error when the task is created? And you said it is only sometimes, that is a bit strange. Then I think there should be some kind of problem in the container maybe for the workflows which go into error.

Regards,

Martin

[Former Member]

I have it....somebody was making changes with user WF-BATCH....

Marin, thank you very much for your ideas....now I am going to kill somebody )..

JJ