Skip to main content

Run Splitter

After you have selected the input and Configuration, you are ready to run Splitter.

A successful Splitter Run creates outputs that match the intended routing logic and are ready for review by the people who receive them.

Typical run steps​

A typical Run looks like this:

  1. open Splitter
  2. select the input File or dataset
  3. choose the Splitter Configuration
  4. review the output groups and routing Rules
  5. start the Run
  6. inspect the generated outputs
  7. confirm each output contains the expected records

What to check before you run​

Before starting the Run, verify:

1. The input is the correct data​

Confirm that the File is the intended source for the split.

Check items such as:

  • reporting period
  • source system export
  • business unit or operating context
  • File freshness
  • whether the File has already been filtered or cleaned

2. The configuration matches the routing goal​

Make sure the selected Configuration creates the outputs you need for the current workflow.

This matters when similar configurations exist for different teams, destinations, or reporting periods.

3. You know what each output should contain​

Before the Run begins, decide how you will review the result.

Examples:

  • expected output groups should be present
  • known sample Records should land in the right output
  • exception Records should be isolated
  • output counts should be reasonable for the business context

Review the result after the run​

After processing finishes, inspect each output deliberately.

Review:

  • Record counts for each output
  • known Records in each group
  • boundary cases
  • blank or unusual routing values
  • Records in any exception or unmatched output

If records went to the wrong output​

Investigate one example Record at a time.

Common causes include:

  • source values were formatted differently than expected
  • a routing value was blank or misspelled
  • rule order or overlap affected the result
  • the wrong Configuration was selected
  • the business Rule changed but the Configuration was not updated

If the source value is inconsistent, clean it first and rerun the split.

If an output is unexpectedly empty​

An empty output can be valid, but it should be reviewed.

Check whether:

  • the input actually contains records for that group
  • the routing rule is too narrow
  • the source values changed
  • the output group is no longer needed

Final checkpoint before downstream use​

Before sharing or uploading the generated outputs, confirm:

  • the correct input was used
  • the intended configuration was run
  • every output was reviewed
  • unmatched or exception Records have a clear next step
  • the results make business sense