Kylo job keeps running on a processor which doesn't handle exceptions

Description

When you have a processor in a flow which fails on some exception which is not propagated to any of the processor's relationship (e.g. processor doesn't have a failure relationship or it doesn't expect exceptions and doesn't handle them; processor which meets both conditions is for example UpdateAttribute processor) such processor is not marked in the feed job's details as failed and such job runs indefinitely.

Also this failing processor generates a lot of messages which are sent to message queue and can make it stuck (see attached screenshot) which then prevents Kylo for reporting job status for other feeds.

Environment

None

Assignee

Unassigned

Reporter

Robert Hencz

Labels

None

Reviewer

None

Story point estimate

None

Components

Affects versions

Priority

High
Configure