Observability

Job Engine v3 Error: ResourceExhausted when GetJobResult exceeds gRPC message size limit in the SolarWinds Platform

This article provides information about a Job Engine v3 error that occurs when a worker returns a job-result response larger than the configured gRPC message-size limit. The failure can prevent Job Engine v3 from processing the job successfully and may be followed by repeated processing attempts, worker instability, or increased memory usage.

First published date

9/10/2026 8:41 PM

Last published date

9/10/2026 8:41 PM

Overview

Job Engine v3 uses gRPC to retrieve job results from worker processes. When the returned result exceeds the configured incoming message-size limit, the request fails with a ResourceExhausted error.

A similar message may appear in the Job Engine or worker logs:

[YYYY-MM-DD HH:MM:SS,mmm] ERROR SolarWinds.JobEngine.Worker.GrpcClient.WorkerGrpcClientExceptionHandler -
The Worker gRPC client encountered an 'RpcException' exception -
'Status(StatusCode="ResourceExhausted", Detail="Received message exceeds the maximum configured message size.")'
Grpc.Core.RpcException: Status(StatusCode="ResourceExhausted",
Detail="Received message exceeds the maximum configured message size.")
   at ...WorkerClient.GetJobResult(...)
   at ...WorkerGrpcClient.GetJobResult(...)
[YYYY-MM-DD HH:MM:SS,mmm] ERROR SolarWinds.JobEngine.Engine.WorkerMonitor -
Attempt to process jobs on worker <worker-id> failed.

Observable platform behavior

The following behavior may be noticed by an administrator or monitoring operator when the affected job or plugin cannot complete successfully:

  • Monitoring data for the affected feature or plugin may stop updating or become delayed.
  • Polling or collection jobs may fail, remain incomplete, or repeatedly retry.
  • Status information, metrics, or alerts that depend on the affected job may be delayed or unavailable.
  • Platform, Collector, or Job Engine responsiveness may degrade if resource usage continues to increase.

These are possible external symptoms and may not occur in every environment. They are not sufficient by themselves to confirm this issue.

Internal indicators

The following internal symptoms may also occur:

  • Job Engine v3 fails to process one or more worker jobs.
  • The same job or worker is processed repeatedly.
  • Worker processes are repeatedly created or remain active after failed processing.
  • Job Engine or Collector memory usage increases over time.
  • Job Engine v3 logs contain repeated GetJobResult and ResourceExhausted messages.

The exact plugin or job that produces the oversized response may vary by environment. Confirm the issue by matching the log error and GetJobResult call rather than by memory symptoms alone.

Product section

Hybrid Cloud Observability

Cause

The error occurs when the response returned by the worker through the unary GetJobResult gRPC operation exceeds the configured incoming gRPC message-size limit.

The default gRPC incoming message-size limit is commonly 4 MB unless it has been changed by the application. The affected response may be generated by a job or plugin that returns a large result. Repeated failures may cause additional worker processing attempts and can contribute to worker churn or increased memory usage.

Resolution

As of September 10, 2026, a permanent fix implementation date has not been defined. Monitor this article and the SolarWinds release notes for product fixes and enhancements.

Temporary workaround for environments using the SD-WAN poller

Use this workaround only when the issue is associated with the SD-WAN poller and disabling that poller is acceptable for the user.

  1. Log in to the SolarWinds Platform Web Console.
  2. Go to the Advanced Configuration page:
    http://<solarwinds_server>/Orion/admin/advancedconfiguration/global.aspx
  3. Search for SolarWinds.JobEngine.Service.v3.Settings.
  4. Locate JobEngineV3PluginList and select the pencil/edit icon.
  5. Copy the current value to a text editor for backup.
  6. Remove the following entry from the list:
    SolarWinds.Orion.SdWan.Pollers
  7. Remove the extra semicolon or separator left in the list.
  8. Save the setting.
  9. When prompted, restart the SolarWinds services.
  10. Confirm that the Collector, Job Engine v3, and Job Engine v2 services restart successfully.
  11. Monitor the Job Engine v3 logs and system memory for recurring ResourceExhausted and GetJobResult errors.

 

Workaround limitations

  • This workaround disables SD-WAN polling and may reduce monitoring coverage.
  • It is a temporary mitigation, not a permanent product fix.
  • Do not apply it when SD-WAN polling must remain enabled without first confirming the user impact.
  • Do not change gRPC message-size settings manually unless SolarWinds Support provides a supported configuration and value.