Article ID: 118932, created on Nov 29, 2013, last review on May 22, 2017

  • Applies to:
  • Operations Automation

Symptoms

  1. "Synchronize resource usage for instances of APS applications" task is failed with timeout error.
  2. There are a lot of APS instances in OA with numerous APS resources provisioned.

Cause

The data of APS instances could not be synchronized due to insufficient task timeout.

Resolution

Use the OA OpenAPI method pem.tasks.rescheduleTask to re-schedule a failed task with a new custom timeout. Read the KB article #115550 for more details about the pem.tasks.rescheduleTask API method.

Important! It is not possible to change the default timeout for an arbitrary periodic or regular task. It means that new task will be scheduled with default timeout - 3600 seconds. In case the issue will reappear, timeout should be increased again.

Additional information

Also see:

"Synchronize resource usage for instances of APS applications" task fails with IDL:omg.org/CORBA/TIMEOUT:1.0

Check "Synchronize resource usage for instances of APS applications" task specification in KB article # 115690

caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF