Workflow stuck

[Former Member]

Hi All,

We are in sourcing 10.0.

I am facing some issue in workflow.

I have written one step approval workflow, comprising one pre and one post script.

Have made an extension collection in contract document and successfully adding approvers through pre-script.

Now mails are getting triggered but after the approval Document is still in locked state .

Phase is not advancing neither going back. I logged in the pots-script but that also logs are not coming when I am checking logs.

Can anyone help me on this, what could be issue.

Thanks in Advance!!

Regards,

Geetika

[former_member207877 · Accepted solution]

Hello Geetika,

Check the below

1) Verify the phase name which you have given in post script logic for changing the phase once the approval process done is valid or not

2) Check the workflow defination rules( i.e, inactive approver role, process owner)

and if it stucked you can unlock the document with process owner.

Regards,

Raj

[Former Member · Accepted solution]

Hi Raj,

Thank you so much  for your input.

I have given all the workflow definitions rule as defined in workflow guide.

Also have cross verify all the phase names, seems all fine.

But the problem is ,I have logged the first line in post-script , that even not coming in logs.

So are  there any other settings needs to be done to run postscript when the document is approved by approver?

Attaching the post script what I have written, if there is nay problem.

Thanks Again:)

Regards,

Geetika

post_phase.txt.zip

[former_member190023 · Accepted solution]

If post-script is not triggering then most likely the issue is in the pre-script.

Check in administrative reports:

• Background Task Status -> Today's Daemon Alerts
  • will show you the error message triggered on the WF if any
• Background Task Status -> Pending Daemon Events
  • as you described the issue you should have one record there for the WF daemon in queue.
  • In general if you have a WF error, the WF daemon reposts itself in the queue (visible in this report) with the action 'retry'. It will retry to execute the failed action (pre/post script).

Bogdan

[Former Member · Accepted solution]

Hi Bogdan,

Many Thanks for your inputs.:)

Able to figure and resolve out issue in script through Today's Daemon Alerts.

Regards,

Geetika