Troubleshooting

Health Check Failing

If the dashboard shows "Integration Warning" or the health status is unhealthy, the periodic health check at /agentfi/health is not returning the expected response.

Possible causes:

• Worker was deleted or disabled. Check that the Worker still exists in your Cloudflare dashboard under Workers & Pages.
• Route was removed. Verify that the routeyourdomain.com/*is still bound to the Worker under Settings → Triggers → Routes.
• DNS changed. If you moved your domain away from Cloudflare DNS, the Worker will no longer intercept requests.
• Cloudflare outage. Checkcloudflarestatus.comfor any ongoing incidents.

Resolution: Re-deploy the Worker from the Integration page using "Redeploy Worker" (automatic method) or download and redeploy manually, then click "Verify" and "Enable."

Verification Fails

When you click "Verify" and it fails, the dashboard is trying to reachhttps://yourdomain.com/agentfi/verifyand expecting a specific JSON response.

Things to check:

• The Client Domain in the Integration settings matches your actual site URL (including https://).
• The Base Path matches the one configured in the Worker script (default: /agentfi).
• The Worker is deployed and the route is active.
• Try visiting https://yourdomain.com/agentfi/verify directly in your browser. It should return a JSON response like:
  {"status":"ok","accountId":"...","timestamp":"..."}

API Token Issues

If you're using the automatic deployment method and encounter token-related errors:

• "Token is invalid or inactive" — the token may have been revoked or expired. Go to the Cloudflare API Tokens page and create a new one.
• "Failed to deploy" or permission errors — your token may not have the right permissions. Use the "Edit Cloudflare Workers" template when creating the token, which grants the necessary Workers script and route write permissions.
• Zones not loading or wrong zones listed — ensure the token is scoped to the correct Cloudflare account. If you have multiple accounts, the token must belong to the account that manages the domain you want to integrate.
• Want to switch to a different token? Click "Disconnect" on the Integration page, then reconnect with the new token.

Worker Not Intercepting Requests

If requests to /llms.txt or/sitemap.xml on your domain are not being handled by AgentFi:

• Check that the Worker route pattern is yourdomain.com/* (with the wildcard).
• The route must be on the same zone (domain) as your site.
• Subdomains require their own route (e.g., www.yourdomain.com/*).
• Check the Worker's real-time logs in Cloudflare dashboard → Workers → [Your Worker] → Logs to see if requests are reaching the Worker.

llms.txt Returns Wrong Content

• If you see your original llms.txt instead of the AgentFi-generated one, check the Discovery Files settings — the management mode may be set to "Original" instead of "Managed."
• If content seems outdated, it may be cached. The cache TTL is 10 minutes. Wait and try again, or add a cache-busting query parameter.