How Pulse works

Reference for behaviour that isn't obvious from the interface.

Automatic issue detection

Pulse checks every model after each sync. Three conditions trigger an issue:

  • Refresh failed — the last refresh ended with an error status in Power BI.
  • Refresh delayed — no successful refresh in the past 24 hours.
  • Schema change — one or more columns disappeared from the model since the last sync.

Each condition creates at most one active issue at a time. Duplicates are suppressed automatically.

Automatic resolve

Issues close themselves. There is no manual resolve button.

  • A refresh failed issue closes when the next refresh completes successfully.
  • A refresh delayed issue closes when a refresh is detected within the 24-hour window.
  • A schema change issue closes when the missing columns reappear in the model.

Resolved issues remain visible in the history — both on the Issues page and on the model's Issues tab.

Suppress

Suppress silences a known issue for 24 hours. Use it when you are already aware of a problem and don't want it generating noise or alerts while you fix it.

  • The issue stays visible, dimmed, with the expiry time shown.
  • No new alerts are sent while suppressed.
  • Auto-resolve still works — if the condition clears before the 24 hours are up, the issue closes normally.
  • After 24 hours the issue becomes active again automatically if the condition still applies.

Suppress is not a substitute for fixing the underlying problem.

Alerts

Alerts are sent once per new issue — when it is first detected. No repeated reminders. Suppressed issues do not trigger alerts.

Channels: email and Telegram. Configured via environment variables on the server.

Sync interval

Pulse polls Power BI on a fixed interval (default: 15 minutes). All data on screen reflects the last completed sync. The timestamp in the model header shows when the data was last fetched.