Troubleshooting
Fixes for the problems people hit most.
- Check that the API key starts with
leap360_and is set in the process that runs the agent. - Check that outbound HTTPS to
b0vyk178b7.execute-api.us-east-1.amazonaws.comis allowed. - Make sure you call the client that
wrapOpenAI,wrapBedrockand the other wrap methods return, not the original. - Turn on debug logging:
new Leap360({ apiKey, debug: true }).
It reads LEAP360_API_KEY, NEXT_PUBLIC_LEAP360_API_KEY, VITE_LEAP360_API_KEY and REACT_APP_LEAP360_API_KEY. For any other name, pass the key to the constructor.
No API key was sent, or its format is wrong. Send it in the x-api-key header.
The kill switch is on for the agent (AGENT_HALT) or the whole project (GOVERNANCE_HALT). A person signed in to the console can restart it from Agents, or from the top bar for the whole project.
You tried to loosen governance with an API key: restart an agent, turn on shadow mode, decide an approval, or change or delete a policy. Do it in the console.
A policy held the call. Approve it in Approvals; the same call can then run for 15 minutes. To wait instead of failing, set approvalWaitMs (JavaScript) or approval_wait (Python).
The project is probably in shadow mode. Check the banner in the Command center, and switch to enforce on the Shadow mode page when you are ready.
The API is serverless, so the first request after a while can take 1 to 5 seconds. Later requests take 200 to 500 ms. In enforce mode, allowed tool calls are decided locally in about 0.7 ms and don't wait for the API.
Still stuck? Email support@leap360.ai.