Question
Arbetsförmedlingen
SE
Last activity: 9 Jan 2025 11:39 EST
Pega RPA workitem doesn't run the code. Resolves directly after start.
Hi,
We're in a urgent need. We're new to Pega RPA. We've deployed our new RPA package to production (not first time).
After previous successful deployment, queue item was picked-up and straight away marked as resolved without code execution. We couldn't find the solution, so re-installed new runtime machine and code worked.
During recent deployment after change request, we're facing the same issue again. Queue item was picked-up, straight away marked as resolved without code execution. This time re-installation didn't work either.
Same code works in test and prod debug. We've checked all possible logs and tried everything we know, but nothing worked.
This is really urgent and any help is really appreciated, thank you!
Best Regards
/Rajesh
Updated: 6 Jan 2025 14:14 EST
Pegasystems Inc.
US
Pegasystems Inc.
US
One thing you can also do assuming your bots are registering, and the bot is the one completing the work item, would be to send the logs with the case. You can do that in the RuntimeConfig with the settings below. I included the commented section, so you can see the different options.
One thing you can also do assuming your bots are registering, and the bot is the one completing the work item, would be to send the logs with the case. You can do that in the RuntimeConfig with the settings below. I included the commented section, so you can see the different options.
<!-- The settings below are for PublishToRobotManager, which controls Operational Reporting and Robot Activity logging. -->
<!-- PublishToRobotManager.Enabled: Indicates if the publisher sends data to Robot Manager. Enable this top-level setting to send data to Robot Manager. -->
<!-- You can enable or disable each of the choices below, but no data is sent if this setting is false. -->
<!-- -->
<!-- HealthStatistics.Enabled: Indicates if the Health Report-related statistics should be sent. -->
<!-- This includes Logins, Robot Runtime version, package name and version, and fatal exceptions. -->
<!-- RobotActivityLog.Enabled: Indicates whether a separate runtime log is created for each robot activity -->
<!-- and attached to the case upon completion of activity. -->
<!-- RobotActivityLog.eventsToLog: Indicates the Case completion status that will cause a runtime log to be attached to a case. -->
<!-- eventsToLog = 0 indicates that logs should not be sent. -->
<!-- eventsToLog = 1 indicates to send a log for robot activities with a status of "DidNotComplete". -->
<!-- eventsToLog = 2 indicates to send a log for robot activities with statuses of "DidNotComplete" and "CompletedWithErrors". -->
<!-- eventsToLog = 3 indicates to send a log all robot activities. -->
<!-- SsoUserIdRule: Indicates the user ID rule that is to be followed by OperationalEvents for the STS server. -->
<!-- Possible values are 'PartialUPN'[user@domain], 'FullUPN'[ Proprietary information hidden], and 'UserName'[user] -->
<!-- UsageStatistics.Enabled: Indicates if the Automation and Activity Usage Statistics events should be sent. -->
<!-- UsageStatistics.PublishInterval: Specifies the interval, in minutes, between publishing usage statistics events to Robot Manager. -->
<PublishToRobotManager enabled="false">
<HealthStatistics enabled="true" />
<RobotActivityLog enabled="false" eventsToLog="1" />
<SsoUserIdRule>FullUPN</SsoUserIdRule>
<UsageStatistics enabled="true" publishInterval="60" />
</PublishToRobotManager>
Updated: 7 Jan 2025 16:01 EST
HCA Healthcare
US
@RajeshS17304030 The issue where the Pega RPA queue item resolves immediately without running the code may be due to incorrect RuntimeConfig.xml settings, such as the wrong StartMethod or missing the correct project path. Ensure the robot is associated with the right workgroup in Robot Manager and the automation package version is correctly mapped. If the issue started after a code change, verify that the main automation entry points are properly defined and there are no unhandled exceptions. Confirm the target application launches correctly and required apps are listed in the RuntimeConfig.xml. Check if the bot has proper credentials and the queue processors are running without errors in Admin Studio. Make sure the bot is registered and active in Robot Manager, with no version conflicts in the package. Reviewing the runtime logs under %AppData%\Pegasystems\RuntimeLogs can help identify errors. Try restarting the runtime machine, clearing cache, and redeploying the package if the issue continues. If the problem persists, contact Pega Support with detailed logs for further assistance
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Pegasystems Inc.
US
@SairohithThis feels like an AI response and is not relevant or helpful for a variety of reasons.
Pegasystems Inc.
US
@RajeshS17304030If this is urgent, please do not hesitate to contact support directly. They can meet with you to resolve issues rather than the limited interaction we can engage in here. If you do open a support request, please list the support request number in the post, so that we can add any resolution for the community.
Arbetsförmedlingen
SE
Thank you @ThomasSasnett and @Sairohith
Issue is resolved. We edited the old version of the code and re-deployed it and it worked.
But the issue was not solved with the modified package, we have removed some .os files which are not required, looks like that has broken something.
But very strange and no clue why it has marked queue items as resolved. I see only activity events from main are logged but not from robot activity. But I couldn't find any potential issues in logs.
It is really interesting to know further about the below, observed from your answers.
- If I enable logs true for PublishToRobotManager and RobotActivityLog, where can I find those logs? in appdata folder or on Robot Manager?
- Can you please help me understand more about the following comment or any links to read about the concepts.
If the issue started after a code change, verify that the main automation entry points are properly defined and there are no un-handled exceptions. Confirm the target application launches correctly and required apps are listed in the RuntimeConfig.xml.
Pegasystems Inc.
US
- They will be attached to the case with that setting. Logs written locally are written to %AppData%\Pegasystems\Logs (if you are still running 19.1, they are written to %AppData%\Pegasystems).
- I believe this response was an AI generated (or at least AI-supplemented response). My take is that if you start seeing issues after a change, it is likely that the change you made was the cause. If your automation was effectively ignoring the work item because you deleted code that would normally have handled it, then it would make sense that the case would advance immediately after being assigned to a bot. Verifying that entry points are defined is meaningless, but what you should do is verify that your ActivityStarted event is connected and goes to the appropriate automation steps to handle your work item. Looking for exceptions in the log is a good idea as it may identify failure points. Confirming the target application launches correctly and required apps...this entire sentence is really unhelpful. There are no required apps listed in the RuntimeConfig.xml. As for the first part of the sentence, if the target app wasn't launching correctly, that would be what you would report as it would indicate something you as the developer would have understood (since you as the developer created the adapter for that application).
@RajeshS17304030 From context clues, I am assuming the following, but please correct any of my assumptions if they are incorrect.
I would suggest starting with bot registration. Is your bot actually registered and ready for work? Second, I would ensure that logging is enabled for both the RPA service and your Runtime. The RPA Service log will tell you any issues if your bot is not registering. The RuntimeLog should be used to see what happens when the assignment is transferred to the automation. You should see your ActivityStarted event fire and can step through the automation steps there to see where your logic is failing.