> ## Documentation Index > Fetch the complete documentation index at: https://docs.fetchhive.com/llms.txt > Use this file to discover all available pages before exploring further. # Troubleshooting > Fix common Hive Agent setup, source, budget, cancellation, trace, and cost issues Use this page when a Hive Agent does not start, pauses unexpectedly, fails during source preparation, or produces confusing logs. ## The run says a Default API key is required Dashboard-started Hive Agent runs require an active workspace **Default** API key. Open [API Keys](../workspace/api-keys), create or reactivate a key, and mark it as the default key for the workspace. Then start the run again. ## Source preparation failed Source preparation runs before planning. If a website or file source cannot be processed, the run fails before the planner starts. Check that: * Website URLs are reachable * Uploaded files are supported: PDF, DOC, DOCX, TXT, MD, CSV, XLS, or XLSX * Knowledge Bases are active * Knowledge Base items still exist * File uploads belong to the same workspace Open the run detail sheet and inspect the source list for the source-specific error. ## The run is blocked A blocked run usually needs budget approval or has reached a budget gate. Check **Budget Settings** on the Hive Agent. If the run crossed the **Budget Hint (USD)** with **Conservative** strictness, approve the magic link or decline it. If the run reached the **Budget Cap (USD)**, approve enough additional budget to leave room for execution, verification, and final composition. A run can block during Compose even after all nodes verified. ## The run failed after max passes The run can stop when it reaches **Max repeat passes** or when final composition fails verification after **Max compose attempts**. If nodes are verified but Compose failed, open the final response section and read the compose issue. The verified node outputs are still available as supporting detail, but the final composed response did not pass the assembly check. Open the run detail sheet and read the verifier rejection reasons. Then tune the stage that caused the failure: * Improve sources or **PLAN** if nodes are unclear * Add tools or change **EXECUTE** if the agent cannot produce the required output * Adjust **VERIFY** if the verifier is too strict or too loose * Adjust **COMPOSE** if verified node outputs are correct but the final response omits, distorts, or formats them poorly * Use **Best effort** if partial verified node output is acceptable before final composition ## The run was cancelled Hard-stop cancellation stops the run quickly and marks remaining node work cancelled. Partial-result cancellation stops new work, lets already-started work finish, and keeps verified node output in the run detail sheet. If cancellation happens during Compose, the in-flight compose attempt may finish, but no further compose attempts are scheduled. The terminal status is still `cancelled`. ## Trace details look delayed or incomplete Child AgentRun traces can arrive after their parent Hive Agent stage. Refresh the detail sheet after the child run finishes. Use the request ID from the log row or stage detail to open the run directly from global search. ## The run cost is higher than expected Check: * **Max Concurrent Nodes** * **Max repeat passes** * **Max compose attempts** * Source preparation costs * Number of planned nodes * Executor and verifier models * Tool calls made by executor nodes * Whether rejected nodes repeated through multiple passes * Whether the final response needed multiple compose attempts Lower concurrency, use a tighter objective, attach fewer sources, set a lower **Budget Cap (USD)**, or use **Conservative** strictness when you want the run to pause earlier. See also: [Budget Approval](./budget-approval) and [Logs](./logs).