Dear Biswajit.
Many thanks for the response and update.
Regarding the observation of the traces I recommend and suggest reviewing the RFC configurations as based upon the exception there is a discrepancy. I've come across issues like this many times before.
Regarding the refresh from a general perspective let us remember the baseline through which it functions and how the smallest discrepancy can obstruct this core functionality.
Firstly upon the initial loading of the UWL it takes a total of 5 minutes for all tasks to be loaded in.
The behaviour is completely normal. The UWL works using two Pull operations. Firstly tasks are pulled
from the backend into the UWL cache. They are pulled a second time from the cache into the UWL User Interface. Due to thisarchitecture there is an inherent delay in the automatic refreshes
of the UWL. There is no way, in the current architecture that the UWL can refresh instantaneously.
This is upon inital load as the cache must be built first upon logon so there will always be a delay. Real time refresh in the latest versions, is only when you complete a task.
Kindly let me know how you get on.
Cheers
Troy Cronin - Enterprise Portal Support Engineer