Data Source Auto-Deactivation
Wallboard automatically stops refreshing data sources that aren't in use, preserving performance. All configuration and data are retained — nothing is deleted.
Two Types of Deactivation
| Type | Trigger | Disable With |
|---|---|---|
| Usage-based | 30 days of no device usage | "Prevent auto-deactivation" |
| Error-based | 25 consecutive refresh failures | "Ignore Error counter" |
note
Both settings are independent — enable both to prevent all auto-deactivation.
What Counts as "In Use"?
A data source is active when all three conditions are met:
- Bound to content (Slide or Playlist)
- That content is assigned to a Channel
- The Channel is playing on at least one online device
Usage-Based Deactivation
| Data Source Type | Deactivation After | Created By |
|---|---|---|
| Standard (JSON, XML, RSS, etc.) | 30 days | Users via Data Sources menu |
| Ad-hoc (Weather, RSS widgets) | Within days | Auto-created via Quick Editor |
Use this for infrequent, seasonal, or critical data sources.
Error-Based Deactivation
Triggers after 25 consecutive refresh failures (unreachable URL, expired credentials, changed data format, etc.). Use this for on-prem services with planned downtime, flaky external APIs, or long-term outages.
You can reactivate a datasource by:
- Manually refreshing it
You can also disable error-based deactivation by:
- Click on the more button
- Select the Edit option
- Find the Continue refreshing despite errors toggle in the Refresh settings
- Change the option
Reactivation
- Automatic — happens instantly when content using the data source plays on a device. No action needed.
- Manual — click Refresh, assign content to a device, or open a content preview.
You can reactivate a datasource by:
- Manually refreshing it
- Assigning the content that uses it to a device, or by opening a preview of that content
You can also prevent auto-deactivation by:
- Click on the more button
- Select the Edit option
- Find the icon in the upper right corner of the datasource editor
- Enable the Prevent auto-deactivation toggle
Quick Reference
| Topic | Detail |
|---|---|
| Standard data source (usage) | 30 days no usage |
| Ad-hoc data source (usage) | Within days |
| Error-based threshold | 25 consecutive failures |
| Disable usage-based | "Prevent auto-deactivation" |
| Disable error-based | "Ignore Error counter" |
| Data preserved? | Yes |
| User notified? | No |
| Cron vs interval schedule impact | None (deactivation is usage-based, not schedule-based) |
note
Internal data sources are not affected — they have no automatic refresh mechanism.