Manual fullfilment tasks are getting discontinued when new request for same endpoint is raised.

[hnalluri94]

Our tasks are automatically discontinued when a user submits a new request for the same endpoint. This scenario involves a disconnected application where manual tasks are generated. Consequently, a single user can submit requests for themselves, and the form's dynamic attribute allows selection of different users' details for the same entitlement.

Does anyone have any ideas on how to prevent the tasks from being discontinued? We need to ensure that these tasks remain active until the request expiry date. Additionally, when a user submits a new request, the old task should not be disconnected.

Old task getting discontinued:

New task :

[naveenss]

Hi @hnalluri94  do you mean to say, a user can submit multiple requests for the same entitlement?

[pmahalle]

Hi @hnalluri94 ,

From this screenshot, seems like request has been raised for same entitlement twice and tasks which were generated for old request got discontinued automatically. You want those tasks should be stay as new and should not discontinued. Is that correct understanding? If yes, why you want multiple pending tasks for same entitlement, any business reason?

Better enable Block any request due to existing request/task in-flight configuration at endpoint level to avoid multiple request for the same entitlement.

[hnalluri94]

Hi Paddy,

Thanks for your response. 

We are allowing user to submit multiple requests for same entitlement types as we have a custom form developed and users can select multiple users in it . Please find the below screenshot.

Here resource type is the entitlement. So entitlement values will be same but the user details will change every time. It will be different user selected.