Share via

Automation Startup Task Fails

CoreyWhitney-1573 0 Reputation points
2024-09-25T20:19:58.0833333+00:00

Automation startup task fails - Bad Request

Status 400 code

{ "Cache-Control": "no-cache", "Pragma": "no-cache", "Strict-Transport-Security": "max-age=31536000; includeSubDomains", "x-ms-ratelimit-remaining-resource": "Microsoft.Compute/GetOperationResource;44,Microsoft.Compute/GetOperationSubscriptionMaximum;14998", "x-ms-need-to-refresh-epl-cache": "False", "x-ms-request-id": "a2f237ec-9ffa-476c-affd-9c81e3c609b7", "x-ms-ratelimit-remaining-subscription-reads": "249", "x-ms-ratelimit-remaining-subscription-global-reads": "3749", "x-ms-correlation-request-id": "94567557-8cc0-490e-8df9-69c3183e1878", "x-ms-routing-request-id": "CENTRALUS:20240925T040424Z:94567557-8cc0-490e-8df9-69c3183e1878", "X-Content-Type-Options": "nosniff", "X-Cache": "CONFIG_NOCACHE", "X-MSEdge-Ref": "Ref A: A60BBB12BD4E46FDA792B4FA97F84D5A Ref B: DM2AA1091214045 Ref C: 2024-09-25T04:04:24Z", "Timing-Allow-Origin": "*", "x-ms-apihub-cached-response": "false", "x-ms-apihub-obo": "false", "Date": "Wed, 25 Sep 2024 04:04:24 GMT", "Content-Length": "537", "Content-Type": "application/json", "Expires": "-1" }

Azure Automation
Azure Automation

An Azure service that is used to automate, configure, and install updates across hybrid environments.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Amira Bedhiafi 41,966 Reputation points MVP Volunteer Moderator
    2026-04-17T19:39:34.6433333+00:00

    Hello !

    Thank you for posting on MS Learn Q&A.

    I think the request sent by the automation task is invalid but the headers you pasted are only the HTTP response metadata. They do not show the real error message. To better understand this, you need the response body from the failed run in the logic app run history.

    In the Azure portal, open the resource and go to automation tasks then open the failed run and inspect the run history.

    and find the failed action and copy the response body and the error details not just the headers.

    Check the task connections and try to authenticate another time or recreate them.

    If this is a VM start or stop task, try the same operation manually with CLI or Portal to confirm the resource itself can start az vm start --name <vm-name> --resource-group <rg> If manual start works then the issue is in the task connection or workflow not in the VM.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.