Workflow Worked only for a While

[Former Member]

Hi Experts,

I have created a workflow and attached it to a phase . The workflow worked fine ,triggered mail to approver etc,but after a while , when I tested again ,the workflow engine was not triggering mail for approver's I have added .But system is locking the document successfully.

I am not even getting option to approve or reject the document after the system lock.(I have not written any code in pre script to lock the document )

I have seen the Pending Daemon Events in background task Status and it is showing that

ODP_EVENT_WORKFLOW_ENGINE event as pending and it's count is increasing when ever I am running a workflow approval project. To my surprise the pending events row is showing blank in the Next Retry Time and the Retry Count. So I think it might not retry.

I have checked the workflow definition, it worked fine in my trial server.

Any help is appreciated.

Regards,

Uday

[Former Member]

Hi Uday,

The issue could be that the workflow engine crashes even before attempting execute your workflow.. May be due to

old version of workflow or another workflow is crashing the workflow engine altogehter..

Add some logs to your workflow prescript and to make sure your workfow is triggered.

Refer to [; . Here I added few tips on going about debugging..

Thanks, Baski

[Former Member]

Hi Baski,

We have tried the same steps, but no luck. We have followed your blog too and posted few doubt in that.In the eso.trace too there is no error entry.

Workflow event that causes this issue removed from the queue. we tried that out also. Once this entry got removed we have again check the daemon tab from system information and selected the workflow checkbox.

Then i tried to execute the one step working XPDL but same situation.System is sendig all email except Workflow one and document getting locked..

I checked daemon registration query output to locate the ODP_EVENT_WORKFLOW_ENGINE. But there is no such entry present.

In the Background Task Status i can see the new line for raised request.

Pl share your view.

Deepak!!!

[Former Member]

Hi,

Based on our inputs it looks like the xpdl that in use is probably corrupt. please check.

In a normal scenario, you shouldn't see an entry in the background task status in "today deamon alerts" report for workflow. If you see an entry there, navigate to the details and some if there are any error details in there..

Thanks, baski

[Former Member]

Hi Baski ,

Thanks for the reply

I have checked the entry in the background task status in "today daemon alerts" and there is no entry present at all.

And I searched for any trash icon to re start the workflow engine or delete the pending event.What I found was ,in background task status under deamon registration I see a event of this type , ODP_EVENT_WORKFLOW_ENGINE , It has heart beat etc. Can I delete that and check ?.If I delete will the engine restart again?. Since it is under Daemon Registration , I am thinking twice.

Please let me know.

Regards,

Uday

[Former Member]

Hi Uday,

Yes, you can be sure the daemon will restart after you delete in the demon registration.. (it may take ~5 minutes)

Not sure when the workflow error was encountered, check to see if there are other alerts in the "all daemon alerts" report. Also verify in the log to see you have any errors in there..

Thanks,

Baski

[Former Member]

Hi Baski ,

I have deleted the daemon , but I am not able to see ODP_EVENT_WORKFLOW_ENGINE in daemon registration under background tasks.Hour's passed by after deleting !,any idea on how to restart?(we are working on Sourcing 7.0) , since it has not restarted yet.

Secondly As mentioned by Deepak , we have checked daemon registration query output to locate the ODP_EVENT_WORKFLOW_ENGINE,but there is no such entry present.The log files also don't contain any errors,have checked it.

And , I have executed the same workflow in UAT box(Sourcing server) , it's working very fine,but the same workflow is showing me problem in my dev box(sourcing server).

Regards,

Uday.

[Former Member]

Hi Uday,

Once you delete a daemon registration from the daemon registration, the daemon will attempt to start in a couple of minutes. Even if the startup failed, it will keep on trying to restart.This is how the fault tolerant behavior is ensured for daemons. You can be certain that deleting a daemon registration is a non issue & probably it has unearthed an underlying issue..

If you don't see the daemon back in there, there seems to be a persistent error in daemon startup. This could be because the workflow event that was already created is attempted to be executed during daemon start up and it is probably crashing the daemon thread.

Check the following:

- In setup>system information>daemons page, make sure the "workflow" daemon category is enabled. Here the daemon enablement is based on daemon category and not per event type.

- go to the pending events list and see if you see any workflow events that are hanging in there.. if that is case see if you can remove it (don't do this if this a production system &/or the document cannot be locked etc..)

- Look at the daemon alerts page again. there should be some errors if the above 2 or true.

- Look at the application logs in setup>system information>logs

Mostly one of the above should give an hint on this behavior..

Thanks,

Baski