---
title: "Troubleshooting Agent calls"
description: "Fixes for common Tooluse.net failures, organized by exact symptom."
---

> Documentation Index
> Fetch the complete documentation index at: https://help.tooluse.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting Agent calls

<h2 id="a-machine-bearer-credential-is-required"><code>A machine Bearer credential is required.</code></h2>
<pre><code class="language-text">A machine Bearer credential is required.</code></pre>
<p><strong>Cause:</strong> <code>/v1/agent/**</code> did not receive exactly one Bearer machine credential.</p>
<p><strong>Fix:</strong> Send one unexpired <code>amq_</code> Agent key for the application in the path.</p>
<p><strong>Verify:</strong> Discover operations with the same key.</p>
<h2 id="this-application-has-no-enabled-configured-operation-with-this-identifier"><code>This application has no enabled, configured operation with this identifier.</code></h2>
<pre><code class="language-text">This application has no enabled, configured operation with this identifier.</code></pre>
<p><strong>Cause:</strong> The operation was disabled, its connection is incomplete, or the ID belongs to another application.</p>
<p><strong>Fix:</strong> Read operation discovery and the application’s connection state; enable only the intended operation.</p>
<p><strong>Verify:</strong> Confirm the operation appears in discovery before invoking it.</p>
<h2 id="insufficient-credit"><code>Insufficient credit</code></h2>
<pre><code class="language-text">This application's unexpired points cannot cover this platform service invocation.</code></pre>
<p><strong>Cause:</strong> Available platform-managed credit is below the reservation amount.</p>
<p><strong>Fix:</strong> Use the owner top-up flow when available, obtain a grant, or attach a BYO connection.</p>
<p><strong>Verify:</strong> Read <code>/v1/applications/{appId}/credits</code> before invoking again.</p>
<h2 id="invocation-remains-unknown">Invocation remains <code>UNKNOWN</code></h2>
<p><strong>Symptom:</strong> The call never becomes <code>SUCCESS</code> or <code>FAILED</code>, and managed credit remains reserved.</p>
<p><strong>Cause:</strong> Tooluse.net cannot prove whether the provider accepted the original request.</p>
<p><strong>Fix:</strong> Do not dispatch another request. Review the original provider fact and use the reconciliation endpoint to <code>settle</code> or <code>release</code> the reservation.</p>
<p><strong>Verify:</strong> The reconciliation list no longer contains the invocation.</p>
<h2 id="that-workflow-could-not-be-read-as-yaml"><code>That workflow could not be read as YAML.</code></h2>
<pre><code class="language-text">That workflow could not be read as YAML.</code></pre>
<p><strong>Cause:</strong> The uploaded <code>text/plain</code> body is invalid YAML.</p>
<p><strong>Fix:</strong> Validate one workflow document, including <code>tenantId</code>, <code>namespace</code>, and <code>id</code>, then upload it again.</p>
<p><strong>Verify:</strong> The response returns the saved revision.</p>
<h2 id="still-stuck">Still stuck?</h2>
<p><a href="/contact/?topic=product">Open the support form</a> and include the request path, HTTP status, request or invocation ID, and redacted response. Never send credentials or provider response bodies.</p>

Source: https://help.tooluse.net/operate/troubleshooting/index.mdx