This content has been marked as final. Show 3 replies
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.
Sarath,1 person found this helpful
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.