Search Engine: Elastic

Article ID: 131358, created on Aug 26, 2017, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 7.1


A periodic task with the name Office 365 Synchronization with Office 365 Portal fails sometimes with 45 minutes timeout.


When the task satrts, it runs the following query to the Office 365 endpoint: /aps/2/resources/ca97eb1d-3aa5-44c5-85f8-53fe5dd05f0a/azureSynchronize, and waits for its completion.

At this query execution, a block of 100 (or less) most outdated tenants is taken and processed. The query duration depends on amount of the objects to sync, such as users, domains, etc. Sometimes the quey execution time runs out of the default REST timeout of 45 minutes, therefore the task does not receive a response, despite the sync itself was successful:

2017-08-20 20:51:27,972 [  19] DEBUG aps_endpoint: 6363885908797297207 - Request: GET
2017-08-20 21:48:36,223 [  19] DEBUG aps_endpoint: Office365AppController.AzureSynchronize finished


Such timeout error can be ignored, since it does not affect the synchronization process. However, the timeout issue can be fixed by increasing REST timeout value:

  1. Use python script on OA Management Node to set the required timeout for the operation to 1 hour:

    # python 60
  2. Restart pa-agent service (no need to restart pau, it is only needed to reload SaaS):

    # service pa-agent stop
    # service pa-agent start

See also:

KB130404: fails in 45 minutes: No message recieved

0871c0b47b3b86ae3b1af4c2942cd0ce caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 1941880841f714e458ae4dc3d9f3062d 8c199f0ee4305da1a577740620df4a51

Email subscription for changes to this article
Save as PDF