Stitch Fails with “Failed to Find Any Relevant Examples” and Customer 360 Shows Blank Customer Fields

Customers may encounter issues where the Stitch process or Customer 360 database generation fails with messages such as:

  • “Generating Stitch report: Failed to find any relevant examples!”

  • Validation errors related to unresolved columns (e.g. order_item_id).

  • Customer-related fields appear blank when joining Customer_360 with unified_itemized_transactions or unified_customer.

These issues are commonly caused by transient data conditions, misconfigured joins, or records with missing key identifiers.

 

Symptoms

  • Stitch workflows fail intermittently, but manual runs may succeed.

  • Customer 360 tables generate successfully, but:

    • Joins with Customer_360 return blank customer fields.

  • Validation errors referencing missing columns or unresolved identifiers.

  • Low stitch counts (e.g. very few stitched records, high deduplication rate).

     

Root Causes

  1. Temporary Data Conditions

    • Stitch jobs may fail with “Failed to find any relevant examples” when no new or matching data is available in the run window.

  2. NULL Identifiers in Transaction Tables

    • A small number of records may contain NULL values for both amperity_id and order_id.

  3. Feed Configuration & Semantic Tag Issues

    • Feeds are tagged with txn-item semantics and may unintentionally contribute incomplete transactional data.

 

How to Fix

Step 1: Update Join Logic in Unified_Transactions . This prevents invalid records from being treated as duplicates and resolves Customer 360 join issues.

Step 2: Filter Upstream Feeds - Apply filters in the feeds to remove records with NULL order_id

Step 3: Review Semantic Tags - Confirm that only valid transactional feeds are tagged. 

Step 4: Rerun Stitch - After applying the above changes:

  • Run a manual Stitch job.

  • Confirm that the Stitch report is generated.

  • Validate that Customer 360 joins now return populated customer fields.

 

Additional Notes

  • If Stitch fails with “Failed to find any relevant examples”, try running a manual Stitch. This error is often transient and occurs when no new changes are detected.

  • Always verify that key identifiers (amperity_id, order_id) are populated in all transaction-level feeds.