You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/automation/automation-dsc-getting-started.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: This article tells how to do the most common tasks in Azure Automat
4
4
services: automation
5
5
ms.subservice: desired-state-config
6
6
ms.custom: devx-track-arm-template
7
-
ms.date: 10/22/2024
7
+
ms.date: 01/01/2025
8
8
ms.topic: how-to
9
9
ms.service: azure-automation
10
10
---
@@ -281,8 +281,7 @@ You can see the following status information for the corresponding consistency c
281
281
You can also select **View raw report** to see the actual data that the node sends to the server. For
282
282
more information about using that data, see [Using a DSC report server][18].
283
283
284
-
It can take some time after a node is enabled before the first report is available. You might need
285
-
to wait up to 30 minutes for the first report after you enable a node.
284
+
It can take some time before the first report is available, after a node is enabled or restarted. You might need to wait up to 30 minutes after you enable a node or restart a node.
286
285
287
286
## Reassign a node to a different node configuration
0 commit comments