Idle Suspension

Overview

To optimize resource usage, Chelar automatically suspends containers that have been idle for 72 hours — unless they have active proactive features (cron jobs or heartbeat).

How It Works

1. Active — Your container is running and processing messages normally.
2. Idle countdown — After 72 hours with no incoming messages or scheduled tasks, the container is marked for suspension.
3. Suspended — The container is stopped. Your data and configuration are preserved on encrypted storage.
4. Auto-resume — When a new message arrives on any connected channel, Chelar automatically restarts your container. The first message may take a few seconds longer as the container boots.

Keeping Your Container Always-On

If you need your container running 24/7:

• Add a cron job — any active cron schedule keeps the container always-on.
• Enable heartbeat — a lightweight keep-alive that prevents suspension.

What's Preserved During Suspension

Everything. Your container's data lives on encrypted JuiceFS storage, not inside the container:

• Chat history and memory
• Channel credentials (WhatsApp sessions, bot tokens)
• Configuration and plugins
• Workspace files