Ensure the Content-Type is set to application/json (or the required format) and that the User-Agent is not being blocked. Summary Checklist Potential Cause Action Item API Outage Check the provider's status page. Expired Token Generate a new Access Token. Timeout Increase the timeout limit in your HTTP client. Throttling Reduce the frequency of your requests.
Most job scheduling systems enforce session timeouts. If the client application holds a stale authentication token (e.g., after overnight inactivity) and attempts to call capi/jobrequestuserstats , the server rejects it with a generic failure code. capijobrequestuserstats - server response failed 2
The most common cause for "Response Failed" errors is an . Ensure the Content-Type is set to application/json (or
If the API is built on WCF with NetTcpBinding or BasicHttpBinding , a mismatch in data contract versions between client and server can lead to a deserialization exception on the server side. The server sends back a fault envelope, but the client expects a different schema – triggering the "failed 2" catch-all. Timeout Increase the timeout limit in your HTTP client
Proxies or load balancers might strip or modify HTTP headers (e.g., Content-Type , Authorization ), causing the server to parse the request incorrectly. The server then responds with an error that the client cannot interpret.