Working with workflow gets tough when we get errors which are hard to debug. I am working on a workflow yielded error as mentioned above. Everything is right about package.
First Thing to Check
1. Whether the package is Valid or not and it is in Valid state
Reason for the Error
As I am modifying a workflow, it works well for certain instances. When I modify the package and recompile it, I am facing similar issue. Recompilation of package spec/body called through workflow is the main reason for this error. This happens because workflow fails to look at the new status of the package after compilation and it looks at the old data
Solution
1. Get your DBA to bounce the instance
or
2. Restart the notification mailer and Service Components
or
3. Kill Active Sessions of workflow and drop the package and recompile it then force reload your workflow in the database
First Thing to Check
1. Whether the package is Valid or not and it is in Valid state
Reason for the Error
As I am modifying a workflow, it works well for certain instances. When I modify the package and recompile it, I am facing similar issue. Recompilation of package spec/body called through workflow is the main reason for this error. This happens because workflow fails to look at the new status of the package after compilation and it looks at the old data
Solution
1. Get your DBA to bounce the instance
or
2. Restart the notification mailer and Service Components
or
3. Kill Active Sessions of workflow and drop the package and recompile it then force reload your workflow in the database
I Think it will be safer (and easier) to just "compile the APPS Schemas"
ReplyDeleteas the note 430862.1 suggests