Question
5
Replies
159
Views
Virtusa Corportaion
Posted: September 21, 2016
Last activity: September 22, 2016
Closed
'can't save' error during skim
We are seeing a very specific error when skimming. The error is repeated for five flow rules where 'wait' shapes are employed. However, if we perform a 'save as' action, no errors are displayed. Please see the attached. What is causing this?
***Updated by moderator: Lochan to add Categories***
Moderation Team has archived post,
Close popover
This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 4 years ago
I checked, and the batch requestor rule has access to the application with the rulesets being skimmed. Btw, other rules are skimmed without issue - hundreds of rules from the same ruleset.
Posted: 4 years ago
Does the access group for the batch requestor have access to the ruleset associated with the pyContinueAfterWait flow action?
Posted: 4 years ago
I'm not sure why you would get the error then. Maybe someone else has seen this before.
Hi,
I just tried a skim on my 7.1.9 system and didn't have any problems with flows that have a wait shape. I traced the process and see the PegaRULESMove_RunBachReq activity is executed to run the skim using a batch requestor. Can you check your batch requestor rule to see if it could be related to the access group specified for the requestor?