memdocs icon indicating copy to clipboard operation
memdocs copied to clipboard

Specify action to take when agent becomes unresponsive

Open iye-ms opened this issue 9 months ago • 6 comments

Specify action to take when agent becomes unresponsive

iye-ms avatar Apr 14 '25 19:04 iye-ms

@iye-ms : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

prmerger-automator[bot] avatar Apr 14 '25 19:04 prmerger-automator[bot]

Learn Build status updates of commit 8cd1647:

:white_check_mark: Validation status: passed

File Status Preview URL Details
intune/intune-service/apps/lob-apps-macos-agent.md :white_check_mark:Succeeded

For more details, please refer to the build report.

For any questions, please:

Learn Build status updates of commit a25242b:

:white_check_mark: Validation status: passed

File Status Preview URL Details
intune/intune-service/apps/lob-apps-macos-agent.md :white_check_mark:Succeeded

For more details, please refer to the build report.

For any questions, please:

Learn Build status updates of commit 92d338c:

:white_check_mark: Validation status: passed

File Status Preview URL Details
intune/intune-service/apps/lob-apps-macos-agent.md :white_check_mark:Succeeded

For more details, please refer to the build report.

For any questions, please:

#sign-off

Erikre avatar Apr 14 '25 22:04 Erikre

#sign-off

Erikre avatar Apr 15 '25 16:04 Erikre

Hi,

This PR has been open for an extended period of time and has conflicts. If these changes are still relevant, please re-submit them to https://github.com/MicrosoftDocs/memdocs-pr.

Thanks, @v-smandalika

v-smandalika avatar Sep 16 '25 07:09 v-smandalika

Learn Build status updates of commit 92d338c:

:x: Validation status: errors

Please follow instructions here which may help to resolve issue.

File Status Preview URL Details
:x:Error Details

  • [Error: CannotMergeCommit] Cannot merge commit 92d338c42ca32725aaf4c3bd10d4f9f96a2aedab in branch patch-7 of repository https://github.com/iye-ms/memdocs into branch main (commit dda799f55a6f836134801420e60d21f5df5c7100). Please follow this documentation: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/ to use git.exe to resolve you content conflicts locally and then push to remote.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.