topic Re: BP 8199 Error Post Force Run Schedule in Product Forum

BP 8199 Error Post Force Run Schedule

raghavankit200 — Sat, 07 Feb 2026 22:06:27 GMT

Hi Team,

We are facing a connection timeout issue when we try to force-run a schedule.

Observation:

When we force the schedule during non-peak hours, it runs successfully.
When we force the same schedule during peak hours, it fails consistently.

Error message:

Unhandled exception has occurred in a component in your application.
If you click Continue, the application will ignore this error and attempt to continue.
No connection could be made because the target machine actively refused it
10.145.102.17:8199.

This suggests that the target machine or service is not accepting connections during peak hours, possibly due to:

High load / resource exhaustion
Maximum connection limits reached
Service or port (8199) being temporarily unavailable

Has anyone experienced a similar issue where forced schedules fail only during peak hours?
Any guidance on what to check (service limits, Blue Prism settings, infrastructure constraints, etc.) would be appreciated.

Thanks in advance

Re: BP 8199 Error Post Force Run Schedule

naveed_raza — Mon, 09 Feb 2026 14:32:56 GMT

some times it might due to server load , less spaces in DB,

we also seen this , and our RPA COE team setup a weekly server reboot and quarterly data purge , now we are not facing this issue.

we have around 8 scheduler which runs in every 2 minutes 24/7

Re: BP 8199 Error Post Force Run Schedule

raghavankit200 — Wed, 11 Feb 2026 06:28:21 GMT

We have started server reboot 3,4 times a week. Tried data purging too, but the issue remains constant. Any other suggestion please.

Re: BP 8199 Error Post Force Run Schedule

hossein.azimi — Tue, 24 Feb 2026 22:22:17 GMT

Hello raghavankit200

Thank you for contacting Blue Prism Community.

The Core Issue can be:
The error "actively refused it" means the target server (10.145.102.17:8199) received the request but deliberately rejected it because it was too busy or unavailable.

Likely Causes (Peak Hours Only)

1) Resource Exhaustion: The target machine hits 100% CPU/RAM or a full network queue, forcing the OS to reject new connections.

2) Connection Limits: Blue Prism's "Max Connections" limit on the Server or Runtime Resource is reached.

3) Service Instability: The application on port 8199 crashes or stops listening under high load.

4) Firewall Throttling: A firewall is rate-limiting traffic due to the high frequency of requests.

Recommendation to check:

1) Monitor Target Machine: Check CPU, RAM, and Event Viewer logs on 10.145.102.17 during failure times.

2) Check BP Config: Verify the Max Connections limit in Blue Prism Server Configuration.

3) Network Rules: Ask the network team if firewalls are rate-limiting port 8199.

Best regards
Hossein Azimi
APJ support team