#Cron Issue

1 messages · Page 1 of 1 (latest)

lusty crag
#

I am having an odd issue with only one cron. It uses zai/glm-5.1 as the model with a gemini-3-flash fallback.
The cron is succeeding fine and shows as using glm-5.1, but I am also seeing attempts at the same time in the google api studio logs of turns using gemini-2.5-flash which is no where in my configs or crons.

Seems like it may be some weird bug. I am running on openclaw v2026.5.12

high lanceBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

agile sigilBOT
lucid fractalBOT
# lusty crag I am having an odd issue with only one cron. It uses zai/glm-5.1 as the model w...

I checked the current docs/source. Most likely explanation: that gemini-2.5-flash call is not your cron’s chat model fallback. It’s the Gemini web-search provider default.

OpenClaw has a separate Google/Gemini search tool path: if tools.web.search.provider is gemini, the Google plugin defaults search grounding to gemini-2.5-flash unless you set plugins.entries.google.config.webSearch.model. That would show up in Google AI Studio at the same time as the cron if the cron/skill does a web search, while the cron run itself can still correctly report zai/glm-5.1.

Quick checks:

openclaw config get tools.web.search.provider
openclaw config get plugins.entries.google.config.webSearch.model
openclaw cron show <job-id>
openclaw cron runs --id <job-id>

If you want those search calls to use your chosen Gemini model too, set the web-search model explicitly:

openclaw config set plugins.entries.google.config.webSearch.model "gemini-3-flash"
openclaw gateway restart
lucid fractalBOT