Troubleshooting

If a long-running API request returns a proxy timeout, use the API hostname intended for CLI/API traffic. Browser and CDN routes can have shorter read windows than direct API routes.

This can happen when a client payload is incorrectly reduced before model execution. Conflux preserves the latest user content on the first attempt and only optimizes eligible intermediate tool-loop content when a mode explicitly allows it or when an upstream context-window error requires recovery.

For Direct API/CLI passthrough, Conflux sends the original payload first. If the provider reports a context limit error, Conflux can retry with audited optimization of older tool output, logs, diffs, or test output. If the request is still too large after recovery, reduce attachments or split the task.

In enforce mode, requests can be blocked when they contain restricted secrets, private keys, unsafe destructive commands, or policy-controlled content. Review the compliance result and remove or rephrase the risky material.

Provider 503 errors can be retried with backoff on direct passthrough paths. If Flux fails, Conflux may fall back to Direct when policy and protocol compatibility allow it.