Workflow Agent determination rule is getting fail despite of valid agent assignment.

[former_member231865]

Hi,

We have a rule that is getting failed each time when it is running in the background.

if we are restarting the workflow manually, It is working fine and routing to correct approvers.

at run time the agent determination is getting failed and the WF goes into an error because of it. However when i restart the WF via SWPR it works well and the agent determination works well either.

Note: Task is defined as general task

Pls suggest what could cause this problem. If there is a problem in responsibility rule then why it works after restarting from SWPR.

[anjan_paul]

Hi,

Please share screenshot of workflow rule binding and runtime workflow log of container value

Thanks

[former_member184495]

Hi WA,

first check why WF going to error, why you need SWPR all the time.

Check your bindings.

Do check the org-unit's validity for that object-id, may it be USER, POSITION or whatever you maintaining.

Hope it helps.

Aditya V

[former_member231865]

Hi Aditya,

If it is binding ,Postion ,user issue then how come it is working when we manually simulating the workflow rule.

[former_member184495]

Hi WA,

reason why I said to check is because you getting error at run-time, may be value which should be passed to the rule isnt.

Aditya V

[former_member231865]

Hi Aditya,

The values are getting passed at the run time, I will share the snapshot soon.

Thank You for the input.

Regards,

Walter

[StephaneBailleu]

Hi

Another guess, try to find if at runtime the value of your criteria (plant) is available, may be you need a small delay to get it available.

Your rule seems to work from the screen shot. if using SWPR it works then the problem is not in the binding itself but certainly in the availability of the values at runtime.

One thing that can help you determine if this is the problem is to add a container in your workflow for the plant and before your dialog step add a container operation from the object attribute to the container plant.

then when you determination fails you can check if the container is filled.

Cheers

Stephane

[former_member467951]

A very wild guess, it could be an authorization issue as the background gets executed under the WFBATCH and the manual execution is your id. Especially if your Rule has some HR info-type reads etc, it is worth checking for access.