Request getting Struck in Wait for Verification.Please tell how to know what the issue is
Apologies if you already know this, but the Pending Verification step means the changes have been marked as Complete (either manually or by AFX) and is now awaiting collection from the target system to verify that the changes have been made.
The reason the request only get marked as Completed once it's been verified against the target system is because although the change is marked as Complete, it may not actually of been successful, for example, an administrator could mark the request as complete but not actually perform the correct action. We refer to this as the closed loop process.
Have you run the associated collector to verify that the changes have actually been made? Have you checked the target system to confirm the changes have been made?
Thanks the information .
No I haven't run the associated collector to verify that the changes have actually been made or not.
But when i checked in user profile the requested access of this particular request had been added to user profile.
Have you since run the collector?
If yes, is the request now marked as Completed?
Instead of running the collector, I mannually completed the Workflow of the request and request moved to completed state
Out of interest, is there any particular reason why you didn't run the collector?
As those Entitlement application name is been changed by some anaylsts , so running the collectors will not have any effect and as access is been added to user so I just moved the request to completed state manually.Is this not an appropriate way,Please advise.
As a one of activity I don't see any issues.
Going forward you obviously want your requests to complete automatically once collection has successfully occured.
Yeah sure, Can you please tell how to find particular collection for the request for troubleshooting the issue?
For the request that got 'stuck', what was it actually requesting e.g. create account, disable account?
Can you share a screenshot of the Change Request?
Clive, mostly this use to occur in Termination request which use to auto trig-erred by AveskaAdmin...sorry now I don't have screenshot of that request as it's been processed, but those requests use to have many applications change requests........
Most of the time these requests are the result of a design problem. The customer does not want to fix the problem (design) they want to fix the consequences of the design.
As Clive noted the intention of the verification is to confirm that the (correct) items was actually created by AFX.
The most common problem is when AFX creates the (correct) item but the collection is not setup correctly to collect it. The failure appears to occur at AFX so this is typically where customers look for an issue, but most often the issue is actually at the collector.
Always make sure that the item that you create in AFX can actually be collected.
Thanks for information , This is really very helpful
Retrieving data ...