Home Discussions Questions & Answers Accuracy of Concurrent Request Conflict Identification

Accuracy of Concurrent Request Conflict Identification

Avatar photoCustomer January 29, 2023 at 3:52 pm

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?

Viewing 4 reply threads
  • Author
    Replies
    • Support January 30, 2023 at 4:39 pm  

      Yes. The report is noted to be highly indicative but may not work 100% reliably because it currently does not consider request set conflicts.

    • Avatar photoCustomer January 31, 2023 at 10:15 pm  

      If a conflicting request is identified, what time metrics does the report use to show the timeframe when the blockage occurred?

    • Support February 1, 2023 at 9:51 pm  

      The report correlates the conflicting requests by tracking those running between the held request’s requested start date and the conflict release date.

    • Avatar photoCustomer February 2, 2023 at 9:07 pm  

      To tune the overall Concurrent Manager environment, besides checking conflicts, what other parameters are considered best practices?

    • Support February 4, 2023 at 9:27 pm  

      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.

Viewing 4 reply threads
  • You must be logged in to reply to this post.

Login with: