openclaw - 💡(How to fix) Fix Lane timeout hardcoded at 630s — not aligned with timeoutSeconds config [1 comments, 2 participants]

TL;DR

Update the src/process/command-queue.ts file to derive the lane timeout from the configurable timeoutSeconds field.

Guidance

• Review the src/process/command-queue.ts file to locate the hardcoded 630-second timeout and consider replacing it with a variable that reads from the timeoutSeconds configuration.
• Verify that the timeoutSeconds field is correctly set to the desired value (e.g., 120s) and that this change does not introduce any other issues.
• Test the updated code to ensure that the lane timeout now aligns with the configured timeoutSeconds value.
• Consider adding a configuration option to make the lane timeout independently configurable, if needed.

Example

// Before
const laneTimeout = 630000; // 630 seconds

// After
const laneTimeout = agentConfig.timeoutSeconds * 1000; // derive from config

Notes

This fix assumes that the agentConfig.timeoutSeconds value is correctly set and accessible within the src/process/command-queue.ts file. Additional testing may be required to ensure that this change does not introduce any other issues.

Recommendation

Apply workaround: update the src/process/command-queue.ts file to use the configurable timeoutSeconds field, as this will help alleviate the issue of stuck sessions and indefinite queuing.