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