How do I handle a model-provider connection error?

Check the work engine’s error and preserve any partial output before retrying. A healthy OfficeCubs marketplace does not establish that an external model service is reachable.

Before you begin

A work engine is the CLI process that performs the task. OfficeCubs supplies the task context and records its progress, while authentication, model availability and usage charges come from your chosen provider. Successful detection is a setup check, not proof that every model or task will work.

Steps

1. Inspect the task’s latest events and terminal.
2. Check the same CLI with a small request in its intended environment.
3. Review any files already written.
4. Retry once the underlying connection works.

Example

If a long report stops after writing an outline, keep that outline and ask a follow-up to continue from the existing file instead of regenerating everything blindly.

Check the result

Verify the new attempt’s result and compare the output directory for duplicate or partial files.

Limits and troubleshooting

A retry may repeat tool actions. Do not assume an external request failed just because its response was lost.