Relationship is not connected and not auto terminated

Modified on Thu, 11 Dec, 2025 at 5:57 PM

Summary

This error appears when a processor has one or more output relationships that are not connected to anything and are not set to auto terminate. Clockspring requires each relationship to be routed or terminated.

Symptom

You see an error similar to:

Relationship success is invalid because it is not connected and is not auto terminated.

The processor remains invalid.

Root Cause

  • A relationship is not routed to another component

  • Downstream processors were removed

  • The processor has multiple output paths but none are handled

  • The processor ends up with unhandled FlowFiles

How to Fix It

Option A: Connect the relationship

Route success, failure, or other relationships to the next processor or a funnel.

Option B: Auto terminate unused relationships

If routing is not needed:

  1. Open the processor

  2. Enable auto termination for unused relationships

  3. Apply changes

Option C: Fix missing downstream components

If a processor was deleted, reconnect or terminate the relationship.

Prevention

  • Handle all relationships when placing a processor

  • Recheck connections after refactoring

  • Auto terminate paths that you do not need

Related Articles

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article