openclaw - 💡(How to fix) Fix [Bug]: Critical Bug - Automated Cron Jobs Not Working [1 comments, 1 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#59615Fetched 2026-04-08 02:42:32
View on GitHub
Comments
1
Participants
1
Timeline
4
Reactions
0
Participants
Timeline (top)
closed ×1commented ×1labeled ×1locked ×1

What Worked Before (Perfectly, for 1 Month) ✅ Daily morning briefing automatically sent every day at 8:00 AM ✅ Hourly automated Kishurit email monitoring and responses ✅ All scheduled tasks executed without any manual intervention ✅ Zero approval requests - everything was automated as expected

What's Broken Now ❌ All automated cron jobs stopped working ❌ Every cron job execution requests approval codes via WhatsApp ❌ Even after approving codes, NEW codes are requested on next run ❌ Messages never get delivered (delivered: false on all runs) ❌ System is stuck in an infinite approval loop

Error Message

Error Pattern in Every Run:

Root Cause

Root Cause (Identified by Your Diagnostic Agent) Cron jobs run in isolated sessions that don't inherit the main agent's elevated permissions or allowlist settings. This appears to be a product bug, not a configuration issue.

Fix Action

Fix / Workaround

What I Need From You IMMEDIATE FIX or a supported workaround Clear timeline for when this will be resolved Refund consideration if this cannot be fixed quickly I was extremely happy with this product when it worked. But right now, I'm considering switching to a competitor because I cannot run my business without automation.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

What Worked Before (Perfectly, for 1 Month) ✅ Daily morning briefing automatically sent every day at 8:00 AM ✅ Hourly automated Kishurit email monitoring and responses ✅ All scheduled tasks executed without any manual intervention ✅ Zero approval requests - everything was automated as expected

What's Broken Now ❌ All automated cron jobs stopped working ❌ Every cron job execution requests approval codes via WhatsApp ❌ Even after approving codes, NEW codes are requested on next run ❌ Messages never get delivered (delivered: false on all runs) ❌ System is stuck in an infinite approval loop

Steps to reproduce

System Information:

Product: Genspark Claw / OpenClaw Gateway v2026.4.1 (da64a97) VM: tomer-5657aeae-5807-vm.westcentralus.cloudapp.azure.com OS: Ubuntu 24.04 LTS Email: [email protected] Broken Cron Job Example:

Job ID: 8d376887-d081-4621-9e28-f2b0a4c920a7 Name: "מעקב מיילים יומי" Schedule: Daily at 08:00 Israel time Status: Runs but never delivers Error Pattern in Every Run:

Copy{ "status": "ok", "delivered": false, "deliveryStatus": "not-delivered", "summary": "נדרש אישור להרצת הפקודות... /approve XXXXXXXX allow-always" } What I've Tried (With Your Technical Support Agent) I spent hours with your diagnostic agent trying to fix this. We attempted:

✗ Changed elevatedDefault from "full" to "on" ✗ Added gsk, bash, and other tools to the allowlist ✗ Modified exec-approvals.json to set defaults to {"exec": "allow"} ✗ Manually added multiple command hashes to allowlist ✗ Restarted gateway service multiple times ✗ Tried approving codes via WhatsApp - generates new codes each time NOTHING WORKED.

Root Cause (Identified by Your Diagnostic Agent) Cron jobs run in isolated sessions that don't inherit the main agent's elevated permissions or allowlist settings. This appears to be a product bug, not a configuration issue.

Impact on My Business 🚨 I cannot use the product as intended 🚨 Automation is the CORE VALUE of this product 🚨 I'm paying for a service that doesn't work

I rely on this system for:

Critical business communications (Kishurit customer inquiries) Daily schedule management Automated workflows that save me hours every day Without automation, this product has NO VALUE to me.

What I Need From You IMMEDIATE FIX or a supported workaround Clear timeline for when this will be resolved Refund consideration if this cannot be fixed quickly I was extremely happy with this product when it worked. But right now, I'm considering switching to a competitor because I cannot run my business without automation.

Expected Behavior Cron jobs should execute without approval requests when:

elevatedDefault: "on" is configured (which it is) Tools are in the allowlist (which they are) The system is configured for automation (which it was, and worked for a month) Additional Information If you need to access my VM for debugging:

FQDN: tomer-5657aeae-5807-vm.westcentralus.cloudapp.azure.com I can provide access if needed

Expected behavior

Impact on My Business 🚨 I cannot use the product as intended 🚨 Automation is the CORE VALUE of this product 🚨 I'm paying for a service that doesn't work

Actual behavior

סוכן לא מבצע משימות

OpenClaw version

01/04/2026+

Operating system

windohs

Install method

claude 4.6

Model

claude 4.6

Provider / routing chain

openclaw genspark

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The most likely fix or workaround involves addressing the isolated session issue for cron jobs, potentially by adjusting the elevated permissions or allowlist settings to be inherited by these sessions.

Guidance

  • Investigate the possibility of configuring cron jobs to inherit the main agent's elevated permissions or allowlist settings, potentially through adjustments in the exec-approvals.json file or other configuration settings.
  • Verify if there are any specific settings or flags that can be applied to the cron jobs to ensure they execute without requesting approval codes, considering the elevatedDefault: "on" configuration.
  • Consider reaching out to the technical support team for further assistance, given the previous interactions and the identified root cause of the issue being a product bug.
  • Evaluate the feasibility of a temporary workaround, such as manually executing critical tasks or exploring alternative automation solutions, to mitigate the impact on business operations.

Example

No specific code example can be provided without further details on the configuration files or the exact commands used for cron jobs. However, the focus should be on ensuring that the cron jobs inherit the necessary permissions and settings to execute without approval requests.

Notes

The provided information suggests a product bug rather than a configuration issue, which complicates the resolution process. The lack of detailed logs or specific error messages related to the cron job executions limits the ability to provide a precise fix.

Recommendation

Apply a workaround, as the issue seems to be related to a product bug that may require a formal fix from the developers. A workaround could involve manual execution of tasks, temporary adjustments to automation workflows, or exploring alternative solutions for critical business operations until a permanent fix is available.

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…

FAQ

Expected behavior

Impact on My Business 🚨 I cannot use the product as intended 🚨 Automation is the CORE VALUE of this product 🚨 I'm paying for a service that doesn't work

Still need to ship something?

×6

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

Back to top recommendations

TRENDING