Investigate an alert
Open the event and the source data needed to understand it.
Turn a data change into a reviewed response.
Signal Flows. Investigate an alert, identify the affected data, and prepare the next step for review.
Product walkthrough. Press Space or Enter to pause or play.
Signal Flows. The alert, investigation, and proposal.
Prepare a response
Use an agent to investigate the issue and propose a specific next step.
Review before changing the system
Inspect the proposal and its supporting records before authorizing a change.
Follow one signal all the way through.
A field rename puts a customer mapping at risk. Follow the evidence into review and the confirmation that an approved proposal was saved.
Orders schema guard watches the source, brings the schema and customer mapping into the investigation, and requires a data operator to review any proposal. Version 3 is confirmed live in this example.
The Orders stream replaces customer_id with customer_reference. Open the run to see the source event and the customer relationship that needs attention.
Read the finding alongside three source references and two checks. The proposed mapping points the customer relationship at the renamed field.
The review brings the evidence, before-and-after preview, and affected items together. A data operator decides whether to save the proposal. No source records would change.
The run waits for confirmation after approval. It completes when the mapping service confirms the proposal was saved. The live mapping remains unchanged; applying it is a separate action.
One signal, one connected response
A field changes. The customer relationship needs attention.
An alert tells you something changed. Signal Flows brings the source, investigation, and proposed response into the same run, so the team can decide with the evidence in view.
In this Orders example, a data operator approves a mapping proposal. The run ends when the mapping service confirms it saved that proposal.
Explore people and agents at workSource event · Orders
The source field was renamed.
Before
customer_idAfter
customer_referenceInvestigate with source evidence
Proposed response · Human review
Update the customer mapping.
Point the customer relationship at customer_reference.
3 source references2 checks
Approved proposal saved
The live mapping and source records stay unchanged. Applying the proposal is a separate action.
Discuss a data alert workflow.
Bring an alert that needs investigation and the response your team usually prepares. We’ll discuss the sources and review steps.