Search Engine: Elastic

Article ID: 120815, created on Mar 31, 2014, last review on Sep 28, 2016

  • Applies to:
  • Operations Automation 5.5
  • Operations Automation 5.4
  • Business Automation 5.5
  • Business Automation 5.4
  • Business Automation 6.0


An APS-related task fails with the following message:

Last execution output Instance of application service with id <ID> does not exist.

Similar error can be also shown when cancelling the subscription on the side of BA.


The instance to which the task is related has already been removed from the Operations Automation (OA) database.

It is likely that the task initially failed with another reason and was then canceled, allowing the next task to be processed, which actually removed the instance from the OA database.


  • Make sure the "finalizing" task has completed. Please see KB #115693 regarding searching for APS tasks.

  • Make sure the instance does not exist in the OA database:

    plesk=> select * from aps_service_instances where service_instance_id = <ID>;
  • All tasks that refer to a non-existing instance can be canceled/deleted.

ac82ce33439a9c1feec4ff4f2f638899 caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e 5b048d9bddf8048a00aba7e0bdadef37 e12cea1d47a3125d335d68e6d4e15e07 198398b282069eaf2d94a6af87dcb3ff 801221f8cd76fba7300d1e6817c8e08b 92711db0799e8aefe8e51f12dace0496 210d017ddc3a076d22f0f865b1cf0730 3627d36199b8ff577605df76e2fa222b bb7e9177fb03488961a3ea554120f328

Email subscription for changes to this article
Save as PDF