Skip to main content

Validate the Data Flow

Configuration is finished when data arrives, not when the form saves. This task runs the workflow once and reads the result in Engage, so that any gap between what the workflow sends and what Engage stores is found now rather than by an operator later.

Before you begin​

Run the workflow​

In Studio, run the workflow once in the environment the integration is being validated in. Note roughly when it ran; you will filter Engage to that time.

Find the records in Engage​

  1. In Engage, select Applications, then the application's row.
  2. In the header, confirm the environment selector reads Development or Production to match where the workflow ran.
  3. In Integration, select the integration. In View, select the view you want to check, or Default View.
  4. Stay on the Overview tab and adjust the date range to include the run.

The table shows one row per record, with Status, TimeStamp, Trace, and then the view's columns in the order you configured them. Search filters the visible rows, and the download control exports them.

What correct output looks like​

Check each of these against the run you made:

  • A row exists for each event the workflow reported. A scheduler event that fires once gives one row at the top level; a message event that fires per iteration gives one row per message at the level whose view carries the message columns.
  • The status is what the workflow set. The Status column shows Success, Failed, or Pending, filterable from the column header. When a workflow reports the same event twice to update a record, the row shows the later status, not two rows.
  • Every mapped column is populated. An empty column on a row whose event carries that field points at the mapping, not the workflow.
  • Drilldown works. On a row whose record has lower-level records, the view control in the Trace column reads Click to view drilldown details; select it to open the next level. A row with none shows No drilldown available for this record.
  • The trace opens. Where a trace was captured, the Trace control reads Click to view trace and opens the execution trace. Development traces are kept for 7 days and production traces for 90; after that the control explains the retention instead.

The Dashboard confirms the same run at a higher level: Total Runs, Total Succeeded, and Total Errored for the selected application or All Applications, and a per-application row with Last Run, Total Runs, Total Succeeded, and Total Errored.

When it does not work​

SymptomCauseWhat to do
No executions found for the selected period. Try adjusting the date or environment filters.The date range or environment excludes the runWiden the range and check the environment selector matches where the workflow ran
The table is empty in the right range and environmentThe integration is InactiveOpen Configure, switch on Enable Integration, and select Update
The table is empty and the integration is ActiveThe workflow's Send to Engage activity is not reporting this application's eventsIn Studio, open the activity and confirm Select Event names an event from this manifest and the Engage context is set
A row exists but its columns are emptyThe event's mapping does not connect the fields to these columnsOpen Map Fields for that event and connect the fields
Two rows where one was expectedThe workflow reported two different events, or the same event with different key valuesUse the same event and the same key values in both Send to Engage calls
A record is missing from a lower levelThe lower view's key columns do not match values the higher level carriesRevisit the key columns in Configure views
Trace shows a retention messageThe trace is older than the environment's retention periodRun the workflow again and check within the retention window

Next steps​

The application is onboarded. Operators can now work in its views; the application page is documented in full under Monitoring. What happens when an execution fails is covered by Managing fallouts and Alerting.