Even after the object is being created in target, task remains in pending tasks

[Suyash_Badnore1]

Hello,

Hope you're doing good!

We're facing one issue while processing new account and add access tasks. When tried to give taskkeys for new account and add access tasks it creates account in the target but task remains in pending tasks only and add access is not getting processed we have to run wsretry once again to process it.

We tried creating 2 separate triggers, one for new account and another for add access and then created a trigger chain and it worked.

But since this cannot be leveraged in production could you please suggest something to get this working as expected?

Regards,

Suyash

[pruthvi_t]

Hi @Suyash_Badnore1 ,

To provide task keys in the trigger for running WSRETRY, you have to run the job manually which would not be the case in production I suppose, unless you have any processes or design requirements which require to run the job manually.

However, did you try to check anything on your end on why the task was remaining in the pending state even after the account is created in the target. Is there anything in the logs or if anything is present in the provisioning comments.

Thanks,

[Suyash_Badnore1]

Hi @pruthvi_t ,

Thanks for responding!

Exactly we can't run the job manually everytime in production to process the tasks.

In the provisioning comments i see that the status is successessful which is expected but in the logs didn't see any erroneous thing which can point to the tasks not getting processed. Is there anything else we can check to get this resolved since this's a critical one.

Please help with the suggestions.

Thanks,

Suyash

[pruthvi_t]

@Suyash_Badnore1 ,

Please check if you've enabled instant provisioning on the applications for which the tasks were created. Also try to test it in lower environment by running the provisioning job without task keys in the trigger and see if you're facing the similar behavior.

Thanks,

[Suyash_Badnore1]

Thanks @pruthvi_t,  will check and update. Currently we're facing some issue once that's fixed will test.

[rushikeshvartak]

Instead of task key go with endpointkey in query

[Suyash_Badnore1]

Thanks @rushikeshvartak  will check and update. Currently we're facing some issue once that's fixed will test.

[Suyash_Badnore1]

Hi @rushikeshvartak ,

When checked by giving the endpoint instead of taskkeys.. Remove account & access tasks are getting processed but when it comes to New account & add acess tasks it still need to be processed by giving the taskkeys separately. Could you please help in understanding why this would be happening and using what we can fix this?

Regards,

Suyash

[Suyash_Badnore1]

Hi @rushikeshvartak  and @pruthvi_t ,

I tried enabling instant provisioning, also checked with endpointkey in the query, and wsretry without giving taskkey it's not working for all the three things.

Wsretry without taskkey is working for remove account and access but for creation it's not processing the tasks.

Please let me know what can fix this, as we're in critical phase.

Regards,

Suyash

[Suyash_Badnore1]

Hello,

Can someone please suggest something to get this going as this's critical implementation for us and we're stuck on this stage where in production we cannot handle this manually.

Regards,

Suyash

[pruthvi_t · Accepted solution]

@Suyash_Badnore1 ,

This needs to be triaged a little deeper with the help of logs. Kindly raise a FD ticket with all the appropriate details like logs, screenshots,taskids etc., so that one of our support engineers can take a look at it.

Thanks,

[Suyash_Badnore1]

Hi @pruthvi_t ,

Thanks, I've created a FD request and hope it gets response with the resolution soon.

Regards,

Suyash