Integration Bus Connector - Gets stuck on failing task

Matt Fothergill asked on October 15, 2018 16:00

I have noticed an issue with one of my integration bus connectors whereby a task that fails then prevents subsequent tasks from being processed.

The connector picks up recent orders and then does some further processing that involves communicating with a third party API / external system.

If a task fails, I would assume the next task in the queue would be processed until all tasks have been processed by the connector. However, it seems that if a task fails it then stops and next time the connector is triggered it starts again from the start of the queue with the failing task and then same again, stops and never gets past it.

The issue is sometimes tasks fail for reasons such as network timeouts and so I would want them to be processed (re-try) next time but sometimes tasks fail for unexpected reasons and need manual intervention but I need the connector to keep processing other tasks in the queue.

Is there something other than returning IntegrationProcessResultEnum.ErrorAndSkip that needs to be done to allow the integration bus to continue with other tasks in the queue for this connector?

Recent Answers

Eric Dugre answered on October 18, 2018 21:01

There was a bug resolved in 9.0.25 that is most likely related to your issue:

"If an integration task failed, processing was blocked for any remaining queued tasks (even if the error was non-critical and logged using the 'ErrorAndSkip' value from the 'IntegrationProcessResultEnum' enumeration)."

0 votesVote for this answer Mark as a Correct answer

Matt Fothergill answered on October 19, 2018 10:21

Thanks Eric. Is there anything I can do to fix the error in Kentico 8.2 until we upgrade?

0 votesVote for this answer Mark as a Correct answer

David te Kloese answered on October 22, 2018 09:42

You're currently out of support (as Kentico supports 3 versions back). With Kentico 12 coming out next month this might be a good moment to upgrade!

Apart from that, a quick check through the Hotfix files mentioned by Eric, it seems it's a change in the core Kentico DLL's which (unless you have the source code license) you can't update.

You could try contacting Kentico support ( directly to see if you can work around it.

Another option is to create a custom tasks that will manually 'repair' integration tasks.

0 votesVote for this answer Mark as a Correct answer

Ivan Louw answered on September 19, 2019 01:07

Hi, I have picked up the same issue in Kentico 12. Is this addressed in the latest hotfix?

Regards, Ivan

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.