openclaw - 💡(How to fix) Fix memory-core dreaming cleanup requires operator.admin and logs failure despite successful promotion [1 participants]

From gateway logs after update to 2026.4.21:

TL;DR

The narrative session cleanup failure can be addressed by either modifying the cleanup process to not require the operator.admin scope or by implementing a fallback to skip cleanup silently when the required scope is unavailable.

Guidance

• Review the memory-core configuration to determine if the operator.admin scope is a strict requirement for narrative session cleanup, and consider relaxing this constraint if possible.
• Investigate the possibility of implementing a graceful degradation or silent skip for cleanup when the operator.admin scope is not available, to prevent repeated failure messages.
• Verify that the managed cron job for memory-core short-term promotion is correctly configured and that the job's permissions are sufficient for the tasks it needs to perform, excluding the cleanup step.
• Consider filing a product issue or feature request to address the underlying problem, as the current behavior may be a design flaw or an oversight in the product's design.

Example

No specific code snippet can be provided without more context about the memory-core and gateway implementation details. However, the solution might involve modifying the cleanup function to check for the availability of the operator.admin scope and handle the case where it's missing, for example:

if has_operator_admin_scope():
    # Perform cleanup with operator.admin scope
else:
    # Either skip cleanup silently or perform a limited cleanup without the operator.admin scope
    pass

Notes

The exact solution will depend on the specific requirements and constraints of the memory-core and gateway systems, including any security or compliance considerations that may dictate the handling of the operator.admin scope.

Recommendation

Apply a workaround by modifying the cleanup process to either not require the operator.admin scope or to degrade gracefully when the scope is unavailable, as this appears to be a product issue rather than a user misconfiguration.