wa-persistence

To keep WhatsApp bot memory persistent across Render restarts, you must migrate storage from ephemeral SQLite to a durable backend like Render Disk, Supabase Pooler, or Render Postgres. This prevents loss of conversations and reminders when ephemeral storage resets.

The best way to migrate WhatsApp bot storage from SQLite to Supabase is using a guided flow that handles Supabase Pooler connections, environment variable management, and manual redeploys to ensure conversational history and reminders survive restarts.

Yes, Render Postgres works as a durable backend for WhatsApp bot memory storage. It serves as one of the explicit sub-flows for migrating from ephemeral SQLite, ensuring that both conversational history and reminders survive server restarts.

Yes, you can skip memory persistence setup for a WhatsApp bot demo by selecting the explicit skip path, which issues a warning instead of migrating storage. This allows quick demonstrations without configuring Render Disk or Postgres backends.

Your WhatsApp bot loses reminders and history after a Render redeploy because ephemeral SQLite storage resets on restart. Migrating to a persistent storage backend like Render Disk or Supabase resolves this data loss.