Discussion

PROBLEMFLOW_ASSIGNMENTOPENFAILFOROPERATOR

PROBLEMFLOW_ASSIGNMENTOPENFAILFOROPERATOR we are getting this error during an Assigment operation and it is defined in Pega-Procom 05-01 . any clue what action/activity is causing this

***Updated by moderator: Marissa to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Comments

Keep up to date on this post and subscribe to comments

August 6, 2008 - 4:24pm

thanks a lot for the suggestions

July 2, 2012 - 5:19am

Can Anyone tell solution about the below issue?

1) how can i reccover the WO and let the flow continue onwards
2) how can debug @ which assignment it failed to write into the DB.

September 24, 2009 - 4:38am

Iam back working on this issue , it seems that while trying to aquire the workobject , the pc_assign_worklist table is being referred to based on the pxinskey from the pc_work ( work object) and since there is no entry for this WO in pc_asign_worklist , pega is spewing up the said error.

now i want to know two things:
1) how can i reccover the WO and let the flow continue onwards
2) how can debug @ which assignment it failed to write into the DB.

Pega
September 24, 2009 - 9:56am

I think it is time you contacted Support.

July 31, 2008 - 8:50am

check the operator accessgroup which ur assigning this work item.

July 31, 2008 - 10:42am

during the work flow, while assigning the work item to either workbasket/worklist you might be missing provide the appropriate workbasket/operator name. If it does not find the required workbasket name (if you routing to workbasket)or opearator name (if you routing to user work list), then it simply run into ProblemFlow process. verify your routing logic implementation.

December 30, 2014 - 12:13pm

Hi

can any one help me about the below error. how to resolve the error

ProblemFlow_StuckFlowConnectorNotFound FORK77 XXXForm

 

 

December 30, 2014 - 1:43pm

Open your flow rule and search for "FORK77" in the flow xml. You should be able to find the when rule name referred in there. As per the error above PRPC is not able to determine which route the workitem should take once it reaches the FORK.