BPA SAP Desktop Agent v3.39.45. The job has been refused error.

[adamharkus]

Since the v3.39.45 update SAP Desktop Agent, I'm getting this error in Desktop agent.

The Job has been refused

This is happening for all my BPA projects, when launching a process or running the automation directly in design mode. Even a very simple one-step test project with a single dialog causes the error now.

So far tried the following:

• Downgraded both the projects and Desktop Agent to the previous, working version. (3.38.59).
• Removing and re-registering the agent in SAP Build
• Uninstalling and re-installing Desktop Agent from scratch.

SAP Build Process Automation 

Any suggestions because at the moment we cannot run an BPA projects.

[Sankara1 · Accepted solution]

Hello Adam,

It seems you are encountering issues with your SAP Build Process Automation (BPA) projects after updating to SAP Desktop Agent version 3.39.45. Here are some steps and considerations to help resolve the issue:

1. Check Supported Desktop Agent Versions

Ensure that the version of the desktop agent you are using is supported. Note that older versions of the desktop agent are supported as follows:

• For Agent 3.x, up to 6 monthly releases can connect or register with SAP Build Process Automation. After 6 months, a desktop agent version is obsolete and is no longer supported. In this case, the agents are updated to the latest version automatically immediately.
• For Agent 2.0.x, up to 12 monthly releases can connect with SAP Build Process Automation, however, Agent 2 is no longer being maintained as of June 30, 2024 
  .

2. Verify Migration Success

Ensure that your migration from Desktop Agent 2 to Desktop Agent 3 was successful. Your existing projects should continue to work as before, and when errors occur, traces should be correctly generated and visible in the cloud

3. Update SDK Packages

Make sure that your Core SDK package version is updated to 1.26 or higher. If your project contains PDF or Document Information Extraction activities, its PDF SDK package must also be updated to version 1.26 or higher. Follow these steps to update your dependencies:

1. In the Overview page of your project, click to open the Project Properties.
2. Select the Dependencies tab.
3. Click Update all SDK so that all of your SDK packages are updated to the latest version.
4. If you're using an RPA tenant: Generate a new package from your project.
5. If you're using an SPA tenant: Redeploy your project 
   Tag3
   .

4. Uninstall Desktop Agent 2

Ensure that the desktop agent 2 is not installed on your computer. It is strongly recommended to uninstall the desktop agent 2 before installing the desktop agent 3. If you need both desktop agents for testing, be aware of the limitations 

5. Restart Desktop Agent

If your project contains an automation and you have tested the automation, your desktop agent might be in Test mode. Restart your desktop agent to end Test mode and run automations 

6. Check Connection Settings

Ensure that Agent service 3 or higher is installed and running 

I hope this helps resolve the issue. Thank you!

[adamharkus · Accepted solution]

Hi Sankara. We have tried all the above and unfortunately have the same issue.

[adamharkus · Accepted solution]

I've now resolved the issue.. In Monitoring > Automation Overview, there were 1000 jobs, the maximum allowed. On further investigation these were scheduled jobs that were running every 5 minutes, so I've seen stopped them.