Reltio Integration Hub

Hi Team,

Requirement: 
When 30K records are sent in a file, the client-side process splits it into three files. For each file, an RIH webhook is triggered. These files need to be processed sequentially, one after another and also all child jobs needs to be completed before triggering the next file, in RIH

Current Design:
We have a main recipe (Recipe 1) that handles business logic.
Recipe 1 calls child recipes to:
Load entity data (Recipe 2)
Load relationship data (Recipe 3)
Trigger the workflow for newly registered profiles (Recipe 4)
All of these are called synchronously. The scheduled runs are working as expected.

Proposed Change:
To support sequential processing, we introduced a webhook-based recipe (Recipe 0) as the parent recipe.
The current main recipe (Recipe 1) was moved under Recipe 0 as a child, with concurrency set to 1.

Issue:
When the webhook is triggered with multiple files, instead of processing them sequentially, Recipe 1 is still running in parallel. This is not the expected behavior.

I understand RIHs concurrency only queues jobs created by scheduling or looping within the recipe, not independent webhook requests.
Can you please let me know if there is any other ways to do it and acheive this requirement?  

Hi Team,

Requirement: 
When 30K records are sent in a file, the client-side process splits it into three files. For each file, an RIH webhook is triggered. These files need to be processed sequentially, one after another and also all child jobs needs to be completed before triggering the next file, in RIH

Current Design:
We have a main recipe (Recipe 1) that handles business logic.
Recipe 1 calls child recipes to:
Load entity data (Recipe 2)
Load relationship data (Recipe 3)
Trigger the workflow for newly registered profiles (Recipe 4)
All of these are called synchronously. The scheduled runs are working as expected.

Proposed Change:
To support sequential processing, we introduced a webhook-based recipe (Recipe 0) as the parent recipe.
The current main recipe (Recipe 1) was moved under Recipe 0 as a child, with concurrency set to 1.

Issue:
When the webhook is triggered with multiple files, instead of processing them sequentially, Recipe 1 is still running in parallel. This is not the expected behavior.

I understand RIHs concurrency only queues jobs created by scheduling or looping within the recipe, not independent webhook requests.
Can you please let me know if there is any other ways to do it and acheive this requirement?  

Hi Team,

Requirement: 
When 30K records are sent in a file, the client-side process splits it into three files. For each file, an RIH webhook is triggered. These files need to be processed sequentially, one after another and also all child jobs needs to be completed before triggering the next file, in RIH

Current Design:
We have a main recipe (Recipe 1) that handles business logic.
Recipe 1 calls child recipes to:
Load entity data (Recipe 2)
Load relationship data (Recipe 3)
Trigger the workflow for newly registered profiles (Recipe 4)
All of these are called synchronously. The scheduled runs are working as expected.

Proposed Change:
To support sequential processing, we introduced a webhook-based recipe (Recipe 0) as the parent recipe.
The current main recipe (Recipe 1) was moved under Recipe 0 as a child, with concurrency set to 1.

Issue:
When the webhook is triggered with multiple files, instead of processing them sequentially, Recipe 1 is still running in parallel. This is not the expected behavior.

I understand RIHs concurrency only queues jobs created by scheduling or looping within the recipe, not independent webhook requests.
Can you please let me know if there is any other ways to do it and acheive this requirement?