---
title: Troubleshooting Workloads
source: https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/workloads/workloads-troubleshooting
---

Use this guide to diagnose and resolve common issues you may encounter while working with Workloads.

## Understanding gaps in service maps [#map-gaps]

When viewing service dependency maps in Workloads, you may occasionally see visual gaps or disconnected service nodes. These breaks usually stem from trace sampling thresholds, missing telemetry along the transaction path, or unsupported entity types.

### Common causes and fixes [#causes-fixes]

**Low trace sampling rates**

If sampling thresholds are too low for a specific service connection, New Relic may lack sufficient trace data during your query window to display the edge between services.

**Fix:** Update your APM agent to the latest version and adjust your sampling configuration to enable enhanced trace sampling.

**Missing telemetry from intermediate services**

A service in the middle of a transaction path may process requests normally but fail to transmit span data to New Relic, breaking the visual chain.

**Fix:** Verify the service is instrumented, check network connectivity and firewall rules, and inspect agent logs for telemetry transmission errors.

**Unsupported entity types**

Certain infrastructure components (such as specific AWS managed services) or custom instrumentations do not support sending span data. In these scenarios, gaps along that specific execution path are expected and cannot be resolved.

No action is required. These gaps reflect the limits of distributed trace instrumentation for that component.

### Why downstream services appear disconnected [#disconnected-downstream]

When an intermediate service in a trace fails to send span data, downstream services do not disappear from your workload — they appear as isolated fragments.

Because these downstream services successfully send trace context to New Relic, they remain visible in your workload. However, without span data from the missing parent service, they lose their visual anchor on the map and appear detached, along with any connected child services they manage.

To resolve disconnected downstream nodes, address the telemetry gap in the intermediate service using the steps above.