Merge pull request #9315 from MicrosoftDocs/main

Auto push to live 2025-07-11 02:38:42

Author: Deland-Han

support/dynamics-365/field-service/mobile-app/webview-reset.md

@@ -3,31 +3,54 @@ title: Home Page Unexpectedly Shown and WebView Reset in Dynamics 365 Field Serv
 description: Helps resolve WebView reset issues in the Dynamics 365 Field Service mobile app.
 author: JonBaker007
 ms.author: jobaker
-ms.reviewer: mhart
-ms.date: 12/12/2024
+ms.reviewer: puneet-singh1
+ms.date: 07/11/2025
 ms.custom: sap:Mobile Application\Application is throwing errors
 ---
-# The Field Service mobile app shows the home page unexpectedly and a WebView reset occurs
+# Troubleshoot WebView reset in Dynamics 365 Field Service mobile app
 
 This article helps you troubleshoot and resolve issues in the [Dynamics 365 Field Service mobile app](/dynamics365/field-service/mobile/overview), where the home page is unexpectedly displayed, and a WebView reset occurs.
 
-## Symptoms
+## What is a WebView reset?
 
-The Dynamics 365 Field Service mobile app unexpectedly displays the home page, and a WebView reset occurs.
+A WebView reset in the Dynamics 365 Field Service mobile app typically indicates that the app module consumes too much memory. It's often triggered by activities that cause memory pressure on the WebView process. [Model-driven applications in Power Apps](/power-apps/maker/model-driven-apps/model-driven-app-overview), such as Dynamics 365 Field Service, run as web applications inside a WebView on the mobile client. As a result, they're subject to the memory management policies of the mobile operating system.
 
-## Cause
+## Root cause
 
-WebView resets for several reasons. When an Android or iOS device runs low on memory, it proactively closes apps to recover memory. Processes that use large amounts of memory include:
+A WebView reset occurs when the mobile operating system terminates an application process that exceeds its memory limits. The threshold for "too much memory" varies by device and operating system, so the issue might not always be reproducible.
 
-- Using the camera and uploading large files such as images, videos, audio, PDFs, or other documents.
-- Customizations like PowerApps Component Framework (PCF) controls. For example, using annotations with custom controls.
-- Sharing screen in Microsoft Teams.
-- Running other apps on the device.
+- **iOS:** The WebView reset error occurs only on iOS because WebViews run in separate processes that can be terminated independently from the main app. If the WebView process exceeds the operating system memory threshold, it's terminated. The app detects this issue, restarts the WebView, and displays a reset message to the user.
+- **Android:** The WebView runs within the main application process. If memory limits are exceeded, the entire app process is terminated, resulting in a crash.
+- **Desktop browsers:** WebView resets don't occur, but memory pressure can still be investigated using browser tools.
 
-## Resolution
+> [!IMPORTANT]
+> Poor memory management in customizations can negatively impact the app experience.
 
-Try the following suggestions to mitigate the issue:
+## Understanding memory pressure
 
-- Determine the cause of the reset. Use developer tools to inspect memory usage in the WebView in the app and browser. For example, [Debug JavaScript in mobile app on Android](/power-apps/developer/model-driven-apps/clientapi/debug-javascript-code#debug-javascript-in-mobile-apps-on-android) or [Fix memory problems](/microsoft-edge/devtools-guide-chromium/memory-problems/).
-- Take steps to reduce memory usage, such as avoiding screen sharing or closing apps other than the Field Service mobile app that use large amounts of memory.
-- Review [performance considerations when customizing the mobile app](/dynamics365/field-service/mobile/improve-mobile-performance) and take actions to reduce memory usage.
+There are two main causes of memory pressure:
+
+1. Memory spike
+
+    A memory spike occurs when a large object is allocated in the WebView process, causing a sudden increase in memory usage. Common causes include:
+
+    - Storing Base64-encoded images or videos in variables within [Power Apps component framework](/power-apps/developer/component-framework/overview) controls or web resources.
+    - Using JavaScript libraries that import large resource files (for example, font libraries.)
+
+    If you can reliably reproduce a WebView reset by performing a specific action (like opening a form or control), a memory spike is likely the cause.
+
+2. Memory leaks
+
+    A memory leak occurs when memory allocated within the WebView process isn't released because of lingering references, such as event listeners or objects that aren't properly cleaned up. This issue prevents the garbage collector from reclaiming the memory, causing memory usage to gradually increase over time. For example, adding event listeners to the window object in JavaScript without removing them when navigating away can lead to leaks. If WebView resets occur randomly and aren't tied to a specific action, it's likely due to a memory leak from previous activities.
+
+## Troubleshooting memory pressure
+
+To diagnose and resolve memory pressure issues:
+
+- For iOS, use Safari memory analysis tools to check the memory performance of your iOS app module. For more information, see [the Timelines Tab in Web Inspector](https://webkit.org/web-inspector/timelines-tab/).
+- The WebView reset error is specific to iOS applications running WebViews and can only be reproduced within that context. However, code that causes memory pressure on mobile also causes memory pressure buildup on desktop browsers. You can investigate the root cause of a WebView reset by using browser developer tools (such as Microsoft Edge DevTools) to track memory usage and identify issues. For more information, see [Fix memory problems in Microsoft Edge DevTools](/microsoft-edge/devtools-guide-chromium/memory-problems/).
+- [Debug JavaScript code for model-driven apps](/power-apps/developer/model-driven-apps/clientapi/debug-javascript-code) to identify problematic scripts or customizations.
+
+## More information
+
+[Performance considerations when customizing the Dynamics 365 Field Service mobile app](/dynamics365/field-service/mobile/improve-mobile-performance)

support/power-platform/power-automate/desktop-flows/troubleshoot-errors-running-attended-or-unattended-desktop-flows.md

@@ -2,7 +2,7 @@
 title: Error code occurs when running an attended or unattended desktop flow
 description: Provides mitigation steps for the error codes that occur when running attended or unattended desktop flows.
 ms.reviewer: cefriant, kenseongtan, guco, johndund, alarnaud, ermathon
-ms.date: 05/29/2025
+ms.date: 07/11/2025
 ms.custom: sap:Desktop flows\Unattended flow runtime errors
 ---
 # Error code occurs when running an attended or unattended desktop flow
@@ -23,6 +23,7 @@ _Original KB number:_   4555406
 |AttendedUserSessionNotActive<br>AttendedUserNotLoggedIn|400|Attended|Check that you're logged in with the correct user and that the session is unlocked on the machine. For more information about the error codes, see [AttendedUserSessionNotActive](troubleshoot-desktop-flow-run-queue-errors.md#attendedusersessionnotactive) and [AttendedUserNotLoggedIn](troubleshoot-desktop-flow-run-queue-errors.md#attendedusernotloggedin).|
 |SessionCreationError|400|Unattended|We couldn't create the session on the machine for an unknown reason. To solve this issue, see [Troubleshoot session creation error codes for an unattended desktop flow run](troubleshoot-session-creation-errrors.md#sessioncreationerror).|
 |SessionCreationErrorWithThirdPartyCredentialProvider|400|Unattended|To solve this issue, see [Troubleshoot session creation error codes for an unattended desktop flow run](troubleshoot-session-creation-errrors.md#sessioncreationerrorwiththirdpartycredentialprovider).|
+|SessionCreationUserPromptedForCredentialsAfterConnection|400|Unattended|To solve this issue, see [Troubleshoot session creation error codes for an unattended desktop flow run](troubleshoot-session-creation-errrors.md#sessioncreationuserpromptedforcredentialsafterconnection).|
 |SessionCreationWinLogonFailure|400|Unattended|We can't create a Windows session to run your unattended desktop flow. You need to restart your machine.|
 |SessionExistsForTheUserWhenUnattended|400|Unattended|Check that you aren't logged in with the same user (regardless of the state of the session) on the machine. For more information about this error code, see [SessionExistsForTheUserWhenUnattended](troubleshoot-desktop-flow-run-queue-errors.md#sessionexistsfortheuserwhenunattended).|
 |UnattendedUserSessionDisconnected|400|Unattended|For more information about this error code, see [UnattendedUserSessionDisconnected](troubleshoot-desktop-flow-run-queue-errors.md#unattendedusersessiondisconnected).|

support/power-platform/power-automate/desktop-flows/troubleshoot-session-creation-errrors.md

@@ -3,30 +3,31 @@ title: Session creation error codes in unattended desktop flow runs
 description: Solves error codes related to session creation during unattended desktop flow runs in Power Automate.
 author: johndund 
 ms.author: johndund 
-ms.date: 04/29/2025
-ms.reviewer: madiazor, guco, fredg 
+ms.date: 07/11/2025
+ms.reviewer: madiazor, guco, fredg, alarnaud
 ms.custom: sap:Desktop flows\Unattended flow runtime errors
 ---
-# Resolve session creation error codes for an unattended desktop flow run
+# Resolve session creation errors for an unattended desktop flow run
 
-This article provides background and potential solutions to the `SessionCreationError` and `SessionCreationErrorWithThirdPartyCredentialProvider` error codes that might occur during an unattended desktop flow run in Microsoft Power Automate.
+This article provides background and potential solutions for session creation errors that might occur during an unattended desktop flow run in Microsoft Power Automate.
 
 _Applies to:_   Power Automate
 
 ## Symptoms
 
-Your [unattended desktop flow run](/power-automate/desktop-flows/run-unattended-desktop-flows) might fail with the `SessionCreationError` or `SessionCreationErrorWithThirdPartyCredentialProvider` error code.
-
-## Cause
-
-When an unattended session is run, Power Automate attempts to create a remote desktop (RDP) session on the target machine. If this session creation fails, you might receive one of the following error codes:
+Your [unattended desktop flow run](/power-automate/desktop-flows/run-unattended-desktop-flows) might fail with one of the following error codes:
 
 - [SessionCreationErrorWithThirdPartyCredentialProvider](#sessioncreationerrorwiththirdpartycredentialprovider)
+- [SessionCreationUserPromptedForCredentialsAfterConnection](#sessioncreationuserpromptedforcredentialsafterconnection)
 - [SessionCreationError](#sessioncreationerror)
 
+## Cause
+
+When an unattended session is run, Power Automate attempts to create a Remote Desktop Protocol (RDP) connection on the target machine. If this session creation fails, you might receive one of the error codes.
+
 ## SessionCreationErrorWithThirdPartyCredentialProvider
 
-This error code occurs because third-party software interferes with Power Automate's ability to create a session on the machine. Power Automate doesn't support some third-party credential providers.
+This error code occurs because third-party software interferes with Power Automate's ability to create a session on the machine. Power Automate doesn't support some third-party credential providers, or might experience conflicts depending on their configuration.
 
 ### Resolution
 
@@ -44,6 +45,72 @@ Each subkey represents an installed credential provider. The following table lis
 | SIDCredentialProvider | 36ED98C6-02FF-47e8-B7FE-957A411CEA16 |
 | CGWinLogon | BDA6DA5B-7E7E-482C-9B3E-67AFF0C838C0 |
 
+## SessionCreationUserPromptedForCredentialsAfterConnection
+
+This error code occurs when the machine prompts for credentials after the RDP connection is established. Power Automate expects credentials to be handled during the connection setup, so this unexpected prompt might cause the flow to fail.
+
+### Resolution
+
+The resolution steps depend on the machine's setup. Follow the instructions to determine the setup and apply the appropriate solution:
+
+[!INCLUDE [Registry important alert](../../../includes/registry-important-alert.md)]
+
+1. Open **Command Prompt** and run `dsregcmd /status`.
+
+2. In the output under the **Device State** section, check the values for `AzureAdJoined` and `DomainJoined`.
+
+   **If `AzureAdJoined: YES` and `DomainJoined: NO`:**
+
+   1. Open **Registry Editor** by pressing Windows+<kbd>R</kbd>, typing `regedit`, and pressing <kbd>Enter</kbd>.
+
+   2. Navigate to the following path:
+
+      `Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services`
+
+   3. Check if the `Terminal Services` key contains a `fPromptForPassword` subkey:
+
+      - If it exists and is set to **1**, contact your IT department to disable the "Always prompt for password upon connection" policy. After the policy is updated, force a policy refresh on the machine.
+      - If `fPromptForPassword` doesn't exist, navigate to:
+
+        `Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp`
+
+        Look for the `fPromptForPassword` DWORD. If it exists, set its value to **0**. If it doesn't exist, create it and set its value to **0**.
+
+   **For other machine configurations:**
+
+   1. Open **Registry Editor** by pressing Windows+<kbd>R</kbd>, typing `regedit`, and pressing <kbd>Enter</kbd>.
+
+   2. Navigate to the following path:
+
+      `Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services`
+
+   3. Check if the `Terminal Services` key contains the following values:
+
+      - `fPromptForPassword` = **1**
+      - `SecurityLayer` = **0**
+      - `UserAuthentication` = **0**
+
+      If all three values exist, contact your IT department to update one of these values:
+
+      - Set `fPromptForPassword` to **0**, or
+      - Set `SecurityLayer` to **1** or **2**, or
+      - Set `UserAuthentication` to **1**.
+
+      If one or more values are missing:
+
+      - Choose one of the missing values based on your requirements.
+      - Navigate to:
+
+        `Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp`
+
+      - Update (or create if not present) the selected value:
+
+         - Set `fPromptForPassword` to **0**, or
+         - Set `SecurityLayer` to **1** or **2**, or
+         - Set `UserAuthentication` to **1**.
+
+3. Restart the machine after making registry changes.
+
 ## SessionCreationError
 
 This error code occurs when a session creation fails for an unknown reason.