openclaw - 💡(How to fix) Fix [Bug]: Gateway restart leaves stale exec config — onRestart passes activate:false to activateRuntimeSecrets [2 comments, 1 participants]

Fix Plan

To address the issue, we need to update the onRestart handler to pass activate: true to activateRuntimeSecrets. This ensures that the latest openclaw.json configuration is loaded and applied after a gateway restart.

Code Changes

// Update onRestart handler to pass activate: true
onRestart: async () => {
  // ...
  await activateRuntimeSecrets({ activate: true });
  // ...
}

Additionally, we should verify that the activateRuntimeSecrets function is correctly loading the latest configuration from openclaw.json.

Verification

To verify the fix, restart the gateway and check that the latest openclaw.json configuration is applied to existing Discord session lanes. You can do this by:

• Checking the gateway logs for any errors or warnings related to configuration loading
• Verifying that the expected configuration changes are applied to the session lanes
• Testing the execution of allowlisted commands to ensure they are executed correctly

Extra Tips

• Make sure to update the internal tracking issue (FR-20260329-002) with the fix details
• Consider adding automated tests to ensure that the onRestart handler is correctly loading the latest configuration
• Review related issues (e.g. #56597) to ensure that this fix does not introduce any regressions.