troubleshooting

Troubleshooting

Agent returns empty response

1. Inspect the agent flow and tools first:
   • list_resources { resourceType: "tool", aiAgentId }
   • duplicate toolId values can cause failed tool execution and empty responses
2. Check LLM exists: list_resources { resourceType: "llm_model", projectId } If none: run setup_llm
3. Check agent description is not empty: get_resource { resourceType: "agent", id }
4. Check endpoint is connected: get_resource { resourceType: "endpoint", id } Verify flowId is set and URLToken exists

create_ai_agent failed

• The tool auto-rolls back created resources on failure. Safe to retry.
• "Could not find entry node": transient issue, retry immediately
• Endpoint step error: check project exists and is accessible

"Resource not found" errors

• All IDs are 24-char hex strings (e.g., 507f1f77bcf86cd799439011)
• UUIDs (36-char with dashes) are referenceIds — most tools need _id, not referenceId
• Use list_resources to find valid IDs

401 / 403 errors, or "who changed this?"

• get_resource { resourceType: "user", id: "me" } returns the account the API key belongs to, plus its roles. Check roles before blaming the API for a 403.
• createdBy / lastChangedBy on any resource are opaque user ids. Never assume one is the current user — compare it to the id from user/me. List responses omit them; read them with get_resource { ..., raw: true }.

Finding the most recently touched resource

• Sort server-side instead of paging through everything and comparing by hand: list_resources { resourceType: "project", sort: "lastChanged:desc", limit: 5 }
• sort takes field:direction and works on any field the resource returns.

setup_llm fails

• See the llm-providers skill for valid provider and model strings
• Verify API key has access to the specified model

delete_resource fails

• Verify the resource ID is a 24-char hex string (not a referenceId UUID)
• Use list_resources to confirm the resource exists before deleting
• Flows, projects and agents are never hard-deleted — delete_resource renames them with a DELETE_ prefix (markedForDeletion: true) so they can be deleted manually in the Cognigy UI. Agent/flow deletion deactivates referencing endpoints (reversible); a renamed project's contents stay live.