Skip to content

Commit 726d499

Browse files
committed
Fixing links
1 parent 997d644 commit 726d499

File tree

2 files changed

+10
-10
lines changed

2 files changed

+10
-10
lines changed

articles/automation/automation-webhooks.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ You can include logic within a runbook to determine if it is called by a webhook
8282

8383
Another strategy is to have the runbook perform some validation of an external condition when it receives a webhook request. For example, consider a runbook that is called by GitHub any time there's a new commit to a GitHub repository. The runbook might connect to GitHub to validate that a new commit has occurred before continuing.
8484

85-
## Creating a webhook
85+
## Create a webhook
8686

8787
Use the following procedure to create a new webhook linked to a runbook in the Azure portal.
8888

@@ -100,7 +100,7 @@ Use the following procedure to create a new webhook linked to a runbook in the A
100100
1. Click **Parameters** to provide values for the runbook parameters. If the runbook has mandatory parameters, you can't create the webhook unless you provide values.
101101
1. Click **Create** to create the webhook.
102102

103-
## Using a webhook
103+
## Use a webhook
104104

105105
To use a webhook after it has been created, your client must issue an HTTP `POST` request with the URL for the webhook. The syntax is:
106106

@@ -125,7 +125,7 @@ Assuming the request is successful, the webhook response contains the job ID in
125125

126126
The client can't determine when the runbook job completes or its completion status from the webhook. It can find out this information using the job ID with another mechanism, such as [Windows PowerShell](https://docs.microsoft.com/powershell/module/servicemanagement/azure/get-azureautomationjob) or the [Azure Automation API](/rest/api/automation/job).
127127

128-
## <a name="renew-webhook"></a>Renewing a webhook
128+
## Renew a webhook
129129

130130
When a webhook is created, it has a validity time period of ten years, after which it automatically expires. Once a webhook has expired, you can't reactivate it. You can only remove and then recreate it.
131131

@@ -194,7 +194,7 @@ else {
194194
}
195195
```
196196

197-
## Testing the sample
197+
## Test the sample
198198

199199
The following example uses Windows PowerShell to start a runbook with a webhook. Any language that can make an HTTP request can use a webhook. Windows PowerShell is used here as an example.
200200

articles/automation/troubleshoot/runbooks.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ When you receive errors during runbook execution in Azure Automation, you can us
2929
* Syntax errors
3030
* Logic errors
3131

32-
2. **Investigate runbook [error streams](../automation-runbook-output-and-messages#runbook-output).**
32+
2. **Investigate runbook [error streams](../automation-runbook-output-and-messages.md#runbook-output).**
3333

3434
Look at these streams for specific messages and compare them to the errors documented in this article.
3535

@@ -39,11 +39,11 @@ When you receive errors during runbook execution in Azure Automation, you can us
3939

4040
4. **Do if your runbook is suspended or unexpectedly fails.**
4141

42-
* [Renew the certificate](../manage-runas-account#cert-renewal) if the Run As account has expired.
43-
* [Renew the webhook](../automation-webhooks#renew-webhook) if you're trying to use an expired webhook to start the runbook.
44-
* [Check job statuses](../automation-runbook-execution#job-statuses) to determine current runbook statuses and some possible causes of the issue.
45-
* [Add additional output](../automation-runbook-output-and-messages#message-streams) to the runbook to identify what happens before the runbook is suspended.
46-
* [Handle any exceptions](../automation-runbook-execution#handling-exceptions) that are thrown by your job.
42+
* [Renew the certificate](../manage-runas-account.md#cert-renewal) if the Run As account has expired.
43+
* [Renew the webhook](../automation-webhooks.md#renew-a-webhook) if you're trying to use an expired webhook to start the runbook.
44+
* [Check job statuses](../automation-runbook-execution.md#job-statuses) to determine current runbook statuses and some possible causes of the issue.
45+
* [Add additional output](../automation-runbook-output-and-messages.md#message-streams) to the runbook to identify what happens before the runbook is suspended.
46+
* [Handle any exceptions](../automation-runbook-execution.md#handling-exceptions) that are thrown by your job.
4747

4848
5. **Do if the runbook job or the environment on Hybrid Runbook Worker doesn't respond**.
4949

0 commit comments

Comments
 (0)