openclaw - 💡(How to fix) Fix [Bug]: session-write-lock timeout (10s) is shorter than legitimate lock holds (40-55s) on v2026.4.29 prep stages — needs config knob [1 comments, 2 participants]

[diagnostic] message processed: ... outcome=error duration=33935ms error="SessionWriteLockTimeoutError: session file locked (timeout 10000ms)" [session-write-lock] releasing lock held for 55611ms (max=15000ms) [trace:embedded-run] prep stages: ... totalMs=113809 [diagnostic] liveness warning: eventLoopDelayP99Ms=44090.5

TL;DR

Increase the session write lock acquire timeout to a value greater than 10s, potentially through a new config knob, to prevent timeouts during slow prep stages.

Guidance

• Review all acquireSessionWriteLock call sites to identify hard-coded timeouts and consider replacing them with a configurable value.
• Evaluate the current default timeout of 10s and consider increasing it to a value between 40s to 60s to accommodate slow prep stages.
• Investigate adding a config key, such as session.lockTimeoutMs or agents.defaults.session.lockTimeoutMs, to allow for customization of the session write lock acquire timeout.
• Test the updated configuration to ensure that interactive Telegram messages no longer fail with "Something went wrong while processing your request" errors during cron/agent prep load.

Example

// Example of using a configurable timeout
const sessionLockTimeoutMs = getConfig('session.lockTimeoutMs', 60000); // default to 60s
acquireSessionWriteLock({ sessionFile: params.sessionFile, timeoutMs: sessionLockTimeoutMs });

Notes

The ideal timeout value may vary depending on the specific use case and performance characteristics of the system. It's essential to monitor the system's behavior after making changes to ensure that the updated timeout value effectively prevents timeouts without introducing other issues.

Recommendation

Apply a workaround by increasing the default timeout value to a higher value, such as 60s, until a config knob can be added to allow for customization. This should help prevent timeouts during slow prep stages and reduce errors.