I am calling an custom plssql package from OA page which in turn starts Workflow and sends notification.
I had to do some changes to workflow file.
I have modified the workflow file and deployed,after new changes,the workflow is not consistent, very often it triggers(there wont be any record in status monitor,out if 10 times ,i see may be once)
Is it necessary to bounce DB tier when we do changes to workflow file?
There is no need to bounce the database every time you modify the WF definition. You may need to add some debugging messages at the moment the workflow process is created/started to determine what the problem is. You can capture the exception message and see what it is about.
STop the Apache and upload the workflow file to you system, then bring back Apache.
We too had some intermittent issues and followed this process.
Let me know if this worked for you.
Hi Thanks for all inputs...
I have put commit after initiating WF in my package then it started working consistently...
Some how when calling from OA Page this inconsistency...when called from Toad it was consistent.