Microsoft Technology Licensing, LLC

Aritra DattaGupta

Michael Nelson

Weizhu Chen

Woo Ram Lee

Ganapathy V Raman

Aarohi Arora

Sparky Toews

Manoj Ajith Prasad

Santosh Vasant Bhosale

Roger F Johnson

Vladyslav Bazyliak

Somak Mitra

Bryan Wilhelm

Will Qian

Benjamin Reich

Matthew Justice

Marwan E Jubran

Vitalii Tsybulnyk

Willy Tanimihardja

Michael J Nelson

Methods for configurable and proactive application diagnostics and recovery are performed by systems and devices. A diagnostics manager determines diagnostics packages corresponding to problems described in client device diagnostics requests. Session identifiers are generated and returned with diagnostics identifiers to clients which then provide the session identifiers and diagnostics identifiers to a service manager for session initiation. Diagnostics packages are located, retrieved, and provided back to the client by the service manager that invokes a client-side engine to execute diagnostics packages. Results are provided to the diagnostics system which determines additional packages to be executed by the engine during the same diagnostics session. Further, device-specific tokens are acquired by client devices which execute local diagnostic packages and acquire remote diagnostic packages for execution in the same session. Additionally, diagnostics packages provide their own user interfaces, and local packages are automatically executed upon invocation of help applications.

System and method for configurable and proactive application diagnostics and recovery

Described herein is a system and method for dependency version conflict auto-resolution for executing job(s). During execution of a particular version of a workflow comprising tasks, information regarding a particular task to be executed is received. The particular task is dependent on another task. Information regarding the dependency is retrieved from a global dependency data structure (e.g., graph) that stores current dependency information regarding the tasks. When it is determined that the conflict exists with respect to the dependency of the particular task on the another task, information regarding the dependency and workflows is retrieved, information regarding a dependency change history regarding at least one of the plurality of tasks, information regarding the particular version of the workflow and a different version of the workflow. A resolution to the conflict can be identified based, at least in part, upon the retrieved information, and, a correct action performed.

Dependency version conflict auto-resolution

Growing community of inventors

Redmond, WA, United States of America

Aritra DattaGupta