BookatlasTwo-Day MuleSoft → Salesforce Bootcamp
13 / 18 · Module 16 — Production Engineering and Observability · filtered: cheatsheet← prev⊞ allnext →

16.18Pool exhaustion symptom

Suppose:

Salesforce itself responds in 300 ms

but Mule request waits 4 seconds before the call even begins.

Possible cause:

connection/resource pool saturation

That is why you want separate:

queue/wait time
downstream execution time

where telemetry allows.