The Synchronize resource usage for instances of APS applications periodic task fails exactly after 8 hours with an output like:
Request has been timed out, details: system exception, ID 'IDL:omg.org/CORBA/TIMEOUT:1.0' TAO exception, minor code = 3e (timeout during recv; low 7 bits of errno: 62 Timer expired), completed = MAYBE
Alternatively, there can be the following output:
The remote server is temporarily down, details: system exception, ID 'IDL:omg.org/CORBA/TRANSIENT:1.0' OMG minor code (2), described as 'No usable profile in IOR.', completed = NO
Due to a large number of APS resources to be updated, request fails with a timeout.
The APS resource usage update procedure will be optimized in scope of APS-41693.
No matter if the task fails, it actually updates the usage of instances, processed prior to the timeout.
The task starts the usage synchronization from the instances which were not processed for a longer time.
Restart the task several times in a row to update the usage of all instances.