Skip to main content

Broken Flow Detection

BreakGround automatically detects flows that break when your application's UI changes. When a CSS selector in a flow step no longer matches any element on the page, the system flags the step and notifies your team.

How Detection Works​

  1. The BreakGround SDK loads on an end user's page and evaluates each flow step's CSS selector against the current DOM.
  2. If a selector does not match any element, the SDK reports the failure back to the BreakGround API.
  3. The API creates a content health issue linked to the specific flow and step.
  4. The flow's health score is recalculated based on the ratio of working to broken steps.

Detection runs passively during normal SDK operation -- no additional configuration is required.

Issue Statuses​

Each detected issue has one of three statuses:

StatusMeaning
OPENThe broken selector has been detected and needs attention.
FIXEDThe selector has been updated and validated as working.
DISMISSEDThe issue has been manually dismissed (e.g., the page was intentionally removed).

Reviewing Broken Steps​

  1. Navigate to Content Health and filter by issues with OPEN status.
  2. Click on a broken flow to see which steps are affected.
  3. Each broken step shows the failing CSS selector and the page URL where the failure was detected.

Fixing Selectors​

To fix a broken step:

  1. Open the flow in the editor.
  2. Navigate to the broken step (highlighted with a warning indicator).
  3. Update the CSS selector to match the new DOM structure.
  4. Save and publish the updated flow.

Alternatively, re-record the step using the Chrome extension to capture fresh selectors.

Re-validating After Fixes​

After updating a selector, click Re-validate on the content health detail page. BreakGround checks the updated selector against the target page and updates the issue status to FIXED if the selector now resolves correctly.

Notifications​

Configure notifications to alert your team when content breaks:

  • Dashboard alerts -- A badge appears on the Content Health sidebar item showing the count of open issues.
  • Email notifications -- Optionally receive email alerts when new broken content is detected. Configure recipients in Settings > Notifications.

Prompt attention to broken flows ensures your end users always receive a working guided experience.