2026-04-09T00:27:04.018+00:00 [WARN] {module:web-session} restored corrupted WhatsApp creds.json from backup
2026-04-09T00:57:08.135+00:00 [WARN] {module:web-session} restored corrupted WhatsApp creds.json from backup

Corruption timestamps show ~30 min interval pattern consistently.

TL;DR

Replace the synchronous file write operation in the auth-store with an atomic write approach to prevent creds.json corruption during Baileys session save operations.

Guidance

• Verify that the auth-store module is indeed using fs.writeFileSync to save the creds.json file, and that this is the only place where the file is being written.
• Implement the suggested fix by replacing the fs.writeFileSync call with the atomic write approach using a temporary file and fs.renameSync.
• Monitor the logs for the restored corrupted WhatsApp creds.json from backup warning to ensure that the corruption issue is resolved after applying the fix.
• Consider adding additional logging or metrics to track the frequency of creds.json corruptions and verify that the issue is fully resolved.

Example

const tmp = credsPath + '.tmp'
fs.writeFileSync(tmp, JSON.stringify(creds))
fs.renameSync(tmp, credsPath)

Notes

This fix assumes that the corruption issue is solely due to the non-atomic write operation. If the issue persists after applying this fix, further investigation may be needed to identify other potential causes.

Recommendation

Apply the suggested workaround using the atomic write approach, as it directly addresses the identified root cause of the corruption issue and ensures that the creds.json file is always written consistently.