IIQ Workflow Issues after DST Time Change

Which IIQ version are you inquiring about?

8.3

Share all details about your problem, including any error messages you may have received.

I am facing an issue with the joiner and leaver workflow, which suddenly stopped working. I have a suspicion but cannot confirm it yet. We recently had a DST time change three days ago, and the server time adjusted accordingly. I suspect this may have caused some issues.

Additionally, I noticed log entries indicating an “early heartbeat” repeatedly.

Could someone please assist in troubleshooting this issue?

Thank you.

Hi @AlaaKhaled

For Early Heartbeat error, please follow the below article:

Early heartbeat warning in IdentityIQ logs - Compass

For the Workflow issue, could you please check your logs or task results to determine if the workflow is triggering as expected? If it is triggering and failing, then check the logs.

Thanks @msingh900 you for your reply.

I checked the article, and the time on all four servers is synchronized.
Regarding the workflow, yes, it is being triggered as expected, but it remains stuck in a pending state.

The unusual part is that when I checked Admin Console → Provisioning → Failures, I selected a user and clicked the help icon on the right. I found the following IQ Service error: “object already exists”.

After that, I ran the Perform Maintenance task, and the joiner process completed successfully instead of staying stuck in pending.

However, I still do not understand why this happened or how to prevent it from happening again. Could you please advise?

Perform maintenance task is required to complete the transaction of workflow, Schedule perform maintenance task every hour or every few minutes based on the number of workflows that gets generated in your env.

Hello @msingh900
how it was working before without scheduling perform maintanance do you have any idea ?

Check your joiner workflow, and see what is the value of optimisticProvisioning, foregroundProvisioning .

Hi @msingh900

Will check this and get back to you , thanks

@AlaaKhaled What there a restart that was done on the IIQ server. You might get the early heartbeat error because of this. If so, stop the IIQ app and kill the rest if there are instances still running. Then restart the app and check