openclaw - 💡(How to fix) Fix [Bug]: Embedded agent Kimi timeout with no fallback despite fallbacks configured in model_stack [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#74985Fetched 2026-05-01 05:39:16
View on GitHub
Comments
1
Participants
2
Timeline
8
Reactions
2
Timeline (top)
subscribed ×4mentioned ×3commented ×1

Code Example

"embedded_run_failover_decision",
"failoverReason": "timeout",
"profileFailureReason": "timeout",
"provider": "kimi",
"model": "kimi-code",
"profileId": "sha256:cf78ee31c9b1",
"fallbackConfigured": false,
"timedOut": true,
"aborted": true
RAW_BUFFERClick to expand / collapse

Problem

Embedded agent sub-sessions repeatedly timeout on kimi/kimi-code with no fallback configured, causing silent failures in isolated cron job sessions.

Steps to reproduce

Run any isolated cron job that uses the embedded agent (e.g., daily-q, nightly review) — these run as sessionTarget: "isolated" with payload.kind: "agentTurn".

Expected behaviour

When the primary embedded model times out, the system should failover to a configured fallback model (sub_agents fallbacks in model_stack include openai-codex/gpt-5.2, openai-codex/gpt-5.4, zai/glm-5).

Actual behaviour

Log shows:

"embedded_run_failover_decision",
"failoverReason": "timeout",
"profileFailureReason": "timeout",
"provider": "kimi",
"model": "kimi-code",
"profileId": "sha256:cf78ee31c9b1",
"fallbackConfigured": false,
"timedOut": true,
"aborted": true

The embedded agent profile for kimi/kimi-code has fallbackConfigured: false despite global model_stack having fallbacks configured. No fallback fires — the job just fails.

Environment

  • OpenClaw: 2026.4.27 (cbc2ba0)
  • OS: Linux x64
  • Node: v24.14.1
  • Session type: isolated (cron job)

extent analysis

TL;DR

Enable fallback configuration for the kimi/kimi-code embedded agent profile to prevent silent failures in isolated cron job sessions.

Guidance

  • Verify that the global model_stack configuration includes fallbacks for kimi/kimi-code, such as openai-codex/gpt-5.2, openai-codex/gpt-5.4, and zai/glm-5.
  • Check the embedded agent profile for kimi/kimi-code and ensure that fallbackConfigured is set to true.
  • Review the cron job configuration to confirm that it is using the sessionTarget: "isolated" and payload.kind: "agentTurn" settings.
  • Test the fallback configuration by intentionally causing a timeout in the primary embedded model and verifying that the system fails over to a configured fallback model.

Example

No code snippet is provided as the issue is related to configuration and not code.

Notes

The issue seems to be specific to the kimi/kimi-code embedded agent profile and the isolated cron job sessions. The solution may not apply to other profiles or session types.

Recommendation

Apply workaround: Enable fallback configuration for the kimi/kimi-code embedded agent profile, as it is the most direct solution to prevent silent failures in isolated cron job sessions.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: Embedded agent Kimi timeout with no fallback despite fallbacks configured in model_stack [1 comments, 2 participants]