Delivery Config

Configure durable inbound delivery for your bot channels — on by default, per-platform isolated

Every bot channel automatically gets crash-safe inbound delivery: a deduplicating journal and a dead-letter queue, stored in ~/.praisonai/state/<platform>/.

from praisonaiagents import Agent

# Durable inbound delivery is on by default — wire an agent in bot.yaml
agent = Agent(name="support", instructions="Reply helpfully on Telegram.")
# praisonai bot start --config bot.yaml

The user starts a bot; durable inbound delivery journals messages and routes failures to a DLQ automatically.

How It Works

What’s on by default

When you start any bot via praisonai bot start, onboard, or bot.yaml, PraisonAI automatically wires:

• Inbound Journal (ingress.sqlite) — deduplicates webhook redeliveries and replays in-flight messages on crash recovery
• Inbound DLQ (inbound_dlq.sqlite) — persists failed-LLM messages for later replay

Both live in one canonical per-platform directory. No configuration needed.

Canonical path

~/.praisonai/state/<platform>/ingress.sqlite
~/.praisonai/state/<platform>/inbound_dlq.sqlite

<platform> is the sanitized platform name (characters outside [A-Za-z0-9_.-] replaced with _).

Set PRAISONAI_HOME to change the base directory:

export PRAISONAI_HOME=/var/lib/praisonai
# → /var/lib/praisonai/state/telegram/ingress.sqlite

delivery: schema

The delivery block is part of each channel configuration in bot.yaml / gateway.yaml:

Quick Start

1. Default (nothing to do)

   Just start your bot — durable delivery is already on.

   praisonai bot start --config bot.yaml

2. Opt out for a channel

   # bot.yaml
   channels:
     telegram:
       token: "${TELEGRAM_BOT_TOKEN}"
       delivery:
         durable: false   # returns to in-memory delivery

3. Override the store directory

   channels:
     telegram:
       token: "${TELEGRAM_BOT_TOKEN}"
       delivery:
         store: /var/lib/praisonai/telegram-state
         # → ingress.sqlite and inbound_dlq.sqlite in /var/lib/praisonai/telegram-state/

Per-platform isolation

Each platform gets its own directory so DLQ replays never cross platforms:

A Discord DLQ replay never consumes a Telegram failed event. Dedup keys never collide cross-platform.

Failure mode

If durability is requested but the SQLite components fail to initialise (permissions, disk full, etc.), _build_durable_components logs a warning and the manager safely falls back to in-memory delivery. Your bot continues working — no crash.

Best Practices

docker run -e PRAISONAI_HOME=/data -v /host/data:/data my-bot

# bot-support.yaml
channels:
  telegram:
    token: "${SUPPORT_BOT_TOKEN}"
    delivery:
      store: /var/lib/praisonai/support-telegram

# bot-sales.yaml
channels:
  telegram:
    token: "${SALES_BOT_TOKEN}"
    delivery:
      store: /var/lib/praisonai/sales-telegram

Related