Home › Discussions › Questions & Answers › Accuracy of Concurrent Request Conflict Identification
Customer · · Questions & Answers · 5 replies
I’m running the FND Concurrent Request Conflicts report to diagnose why some reports are waiting. The results seem mostly accurate, but are there any known limitations to the report’s conflict detection?
Yes. The report is noted to be highly indicative but may not work 100% reliably because it currently does not consider request set conflicts.
If a conflicting request is identified, what time metrics does the report use to show the timeframe when the blockage occurred?
The report correlates the conflicting requests by tracking those running between the held request’s requested start date and the conflict release date.
To tune the overall Concurrent Manager environment, besides checking conflicts, what other parameters are considered best practices?
Tuning best practices include optimizing the number of concurrent processes, tuning the manager’s sleep cycle, and regularly checking for a high number of pending requests.
Sign in with LinkedIn or Google to take part.
