Docs/Discord Analytics/Message history backfill
Discord Analytics

Message history backfill

Message history backfill lets CollabOS scan older Discord messages and add them to the analytics dashboard.

Why backfill is needed

Live tracking starts when the bot is connected and running.

If your Discord server had activity before the bot was connected, older messages will not appear in the dashboard unless you run a backfill.

Backfill helps rebuild historical analytics from previous messages.

What backfill scans

Backfill can scan:

  • text channels
  • announcement channels
  • public threads
  • private threads
  • announcement threads

It ignores:

  • messages older than the selected day range
  • channels the bot cannot access
  • duplicate messages that are already stored

Backfill settings

Days to scan

This controls how far back CollabOS should scan.

Examples:

  • 30 days
  • 90 days
  • 365 days
  • 1500 days

Max per channel

This controls the maximum number of messages CollabOS should fetch from each channel.

For large servers, a higher value gives better coverage but may take longer.

Reset analytics

Reset analytics is optional.

When reset is off:

  • CollabOS keeps existing analytics
  • old messages are added only if they are not already stored
  • duplicate message IDs are ignored

When reset is on:

  • existing Discord message analytics are wiped
  • X link records are cleared
  • member message counts are reset
  • backfill rebuilds analytics from history

Use reset carefully.

Recommended first run

For most teams, start with:

  • days: 30
  • max per channel: 50000
  • reset: false

Use reset only when you want to rebuild the analytics from scratch.

Backfill job statuses

Backfill jobs can show statuses such as:

  • PENDING
  • RUNNING
  • COMPLETED
  • FAILED
  • CANCELLED

The dashboard auto-refreshes backfill jobs so you can see when a job finishes.

When to run backfill

Run backfill when:

  • you just connected a Discord server
  • you want older activity included
  • you need a more complete CSV export
  • you want accurate historical top posters
  • you want inactivity checks to include older message data

If a job fails

A failed job usually means:

  • the bot cannot access a channel
  • the bot is missing permissions
  • the Discord bot is not running
  • the server is not connected
  • Discord rate limits or API issues occurred

Check bot access and try again.

PreviousMember table and filtersNextRecent X links