openclaw - 💡(How to fix) Fix LiveSessionModelSwitchError in isolated cron jobs (v2026.3.28) [1 comments, 2 participants]

TL;DR

The most likely fix involves ensuring that the payload.model override is correctly honored for isolated cron sessions, potentially by revisiting the implementation of PR #47592.

Guidance

• Review the code changes made in PR #47592 to ensure that the fix correctly handles the sessionTarget: isolated configuration and the payload.model override.
• Verify that the agents.defaults.model.primary setting is not interfering with the cron job's ability to use the specified model.
• Test the cron jobs with different model overrides to see if the issue is specific to certain models or providers.
• Consider adding additional logging or debugging statements to understand why some jobs work fine while others fail consistently.

Example

No code snippet is provided as the issue does not contain enough information to create a specific example.

Notes

The intermittent nature of the issue and the fact that some jobs work fine while others fail consistently suggest that there may be a timing or synchronization issue at play. The fix may require a deeper understanding of the underlying system and the interactions between the cron jobs, the agent models, and the session management.

Recommendation

Apply workaround: Revisit and refine the implementation of PR #47592 to ensure that isolated cron sessions correctly use the specified model override, as this is likely to address the root cause of the issue.