Merge pull request #279179 from craigshoemaker/patch-10

[Static Web Apps] Update: Troubleshooting (freshness)

Author: prmerger-automator[bot]

articles/static-web-apps/troubleshooting.md

@@ -5,7 +5,7 @@ services: static-web-apps
 author: geektrainer
 ms.service: static-web-apps
 ms.topic:  conceptual
-ms.date: 04/07/2021
+ms.date: 06/25/2024
 ms.author: chrhar
 ---
 
@@ -23,17 +23,20 @@ npm run build # if specified in package.json
 npm run build:azure # if specified in package.json
 ```
 
-Any errors raised by this process are logged in the GitHub workflow run.
+Any errors raised by this process are logged in the GitHub workflow run. To view the logs generated by build action, use the following steps.
 
 1. Go to the GitHub repository for your static web app.
+
 1. Select **Actions**.
 
     > [!NOTE]
     > Any failed workflow runs display with a red *X* rather than a green check mark.
 
-2. Select the link for the workflow run you wish to validate.
-3. Select **Build and Deploy Job** to open the details of the deployment
-4. Select **Build And Deploy** to display the log
+1. Select the link for the workflow run you wish to validate.
+
+1. Select **Build and Deploy Job** to open the details of the deployment.
+
+1. Select **Build And Deploy** to display the log.
 
     ![Screenshot of the deployment log for a static web app](./media/troubleshooting/build-deploy-log.png)
 
@@ -42,7 +45,7 @@ Any errors raised by this process are logged in the GitHub workflow run.
     > [!NOTE]
     > Some warning error messages may display in red, such as notes about *.oryx_prod_node_modules* and *workspace*. These are part of the normal deployment process.
 
-If any packages fail to install or other issues are raised you'll see the original error messages here, as if you ran the `npm` commands locally.
+If any packages fail to install or other issues are raised, the original error messages are available here.
 
 ### Confirm folder configuration
 
@@ -75,18 +78,22 @@ Use [Application Insights](../azure-monitor/app/app-insights-overview.md) to fin
 > You can only view error messages that are generated after Application Insights is installed.
 
 1. Inside the Azure portal, open the **Resource Group** associated with your static web app.
-1. Select the Application Insights instance, which has the same name as your static web app (if created using the steps above).
+
+1. Select the Application Insights instance, which has the same name as your static web app (if created using the previous steps).
+
 1. Under *Investigate*, select **Failures**.
-1. Scroll down to *Drill into* on the right.
-2. In the lower right corner, under *Drill into*, a button displays the number of recently failed operations.
+
+1. Go down to *Drill into* on the right.
+
+1. Under *Drill into*, a button displays the number of recently failed operations.
 
     ![Screenshot of the failures screen](./media/troubleshooting/app-insights-errors.png)
 
-3. Select **x Operations** to open a panel displaying the recent failed operations.
+1. Select **x Operations** to open a panel displaying the recent failed operations.
 
     ![Screenshot of the operations screen](./media/troubleshooting/app-insights-operations.png)
 
-4. Explore an error by selecting one from the list.
+1. Explore an error by selecting one from the list.
 
     ![Screenshot of the error details screen](./media/troubleshooting/app-insights-details.png)
 
@@ -99,15 +106,19 @@ Application Settings are key/value pairs that set environment variables for your
 When deploying, double check any environment variables are set as Application Settings.
 
 1. Open your static web app in the Azure portal.
+
 1. Select **Configuration**. The *Configuration* screen displays the list of all Application Settings.
 
     ![Screenshot of the Configuration screen on a static web app](media/troubleshooting/app-settings.png)
 
 Use the following steps to add a new variable.
 
 1. Select **Add**.
+
 1. Set the **Name**.
+
 1. Set the **Value**.
+
 1. Select **OK**.
 1. Select **Save**.