Article ID: 118932, created on Nov 29, 2013, last review on May 7, 2014

  • Applies to:
  • Operations Automation 5.4

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 POA.

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

Cause

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

Resolution

Use the POA OpenAPI method pem.tasks.rescheduleTask to re-schedule a failed task with new custom timeout. Refer to POA 5.4 Public API Reference, page 324 for details. Read the KB article # 115550 for more details about the pem.tasks.rescheduleTask API method.

Detailed information about default timeout change for the tasks can be found in KB article # 8138 .

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.

ac82ce33439a9c1feec4ff4f2f638899 caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF