did vco/api/tasks API response change with update?

[jonasloew]

I've got a Workflows which uses 

GET https://{orchestrator_fqdn}/vco/api/tasks/

to get  a list of all Schedules. We recently Updgraded vRA (including vRO) from 8.13.1 to 8.16.0, and now instead of all the Schedules I get the following as a Response to the above Request:

{
  "relations": {
    "total": 0,
    "link": [
      {
        "href": "https://{orchestrator_fqdn}/vco/api/tasks/",
        "rel": "add"
      }
    ]
  }
}

Over the Orchestrator GUI I still see all 21 Schedules.

I checked online and found nothing regarding API changes, the internal doc is also unchanged:
https://{orchestrator_fqdn}/vco/api/docs/index.html#/Task%20Service/getTasks

Can someone help?

[WhiteForEver]

Working for me. I can see all the tasks. You can double check it by running builtin swagger here

[jonasloew]

Thanks for having a look at it. Sadly this still gives no Tasks as a result (see attached image).

[WhiteForEver]

Hm. I have two vRO 8.16.0 instances, and both are ok.

If possible, try to deploy a separate, fresh vRO instance, create some scheduled tasks, and check again. If that works, there is probably something wrong with that particular deployment. 

Another thing I would try is to reboot the vRO using that procedure (it technically destroys and re-deploy all the pods) - https://docs.vmware.com/de/VMware-Aria-Automation/8.16/Administering-VMware-Aria-Automation/GUID-99D...

[jonasloew]

Sadly stopping and starting the vRA Appliance didn't help either.

[WhiteForEver]

Ok. So, if you have an option, please deploy a fresh, test vRO instance and recheck it.

[xian_ · Accepted solution]

Does your user have Orchestrator Administrator role assigned?

Automation Orchestrator user roles and group permissions (vmware.com)

[WhiteForEver]

Yes

[jonasloew]

Very good! No. It's only "Orchestrator Workflow Designer"
That was it! Changing it's Role to "Orchestrator Administrator" helped. Thanks!

[WhiteForEver]

Great. Enjoy 🙂