Abstract: In an example embodiment, a solution is provided that provides an event-driven architecture for scheduling electronic transfers, rather than data-model driven architecture. Doing so allows for the payout portion of the architecture to avoid aggregating transactions—it only needs to obtain an aggregated total (specifically a current balance) once, and thus does not need to be continuously aggregating/checking the aggregation of many transactions simultaneously. The payout portion of the architecture can then forego the traditional ingestion mechanism, which means that it can avoid scanning transaction data.

Abstract: A computing system in a server environment receives a diagnostic data package, corresponding to a problem, from a client computing system and runs a problem-specific analyzer to generate additional problem-specific data. A root cause for the problem is identified along with a recovery action, based on the diagnostic data package and the additional problem-specific data. The root cause and recovery action are communicated to the client computing system.

Abstract: A computing system in a server environment receives a diagnostic data package, corresponding to a problem, from a client computing system and runs a problem-specific analyzer to generate additional problem-specific data. A root cause for the problem is identified along with a recovery action, based on the diagnostic data package and the additional problem-specific data. The root cause and recovery action are communicated to the client computing system.

Abstract: A method, performed by a computing system deployed in a server environment, comprises receiving, from a client computing device that is remote from the server environment, a problem scenario identifier that identifies a problem scenario indicative of a problem associated with the client computing device, identifying a problem-specific diagnostic analyzer, that is specific to the problem associated with the client computing device, based on mapping information that maps the problem scenario to the problem-specific diagnostic analyzer, running the problem-specific diagnostic analyzer to obtain problem-specific diagnostic data that is specific to the problem associated with the client computing device, the problem-specific diagnostic data including first data associated with the client computing device and second data associated with the server environment, identifying a suggested recovery action based on the problem-specific diagnostic data, and communicating the suggested recovery action to the client computin

Abstract: A client computing system detects when a problem is encountered with an application and identified problem-specific diagnostic data that is to be collected, given the detected problem. It also identifies one or more problem-specific test or diagnostic analyzers and executes those analyzers to generate additional data. The data that is collected and the data that is generated by the analyzers is packaged and sent to a service computing system for identifying a remedial action that can be performed to address the problem. The remedial action is received and surfaced for the user.

Abstract: A computing system in a server environment receives a diagnostic data package, corresponding to a problem, from a client computing system and runs a problem-specific analyzer to generate additional problem-specific data. A root cause for the problem is identified along with a recovery action, based on the diagnostic data package and the additional problem-specific data. The recovery action indicates whether it can be performed by an end user or an administrative user. Communication with the end user and administrative user is controlled based on the recovery action.

Abstract: A method, performed by a computing system deployed in a server environment, comprises receiving, from a client computing device that is remote from the server environment, a problem scenario identifier that identifies a problem scenario indicative of a problem associated with the client computing device, identifying a problem-specific diagnostic analyzer, that is specific to the problem associated with the client computing device, based on mapping information that maps the problem scenario to the problem-specific diagnostic analyzer, running the problem-specific diagnostic analyzer to obtain problem-specific diagnostic data that is specific to the problem associated with the client computing device, the problem-specific diagnostic data including first data associated with the client computing device and second data associated with the server environment, identifying a suggested recovery action based on the problem-specific diagnostic data, and communicating the suggested recovery action to the client computin

Abstract: A computing system in a server environment receives a diagnostic data package, corresponding to a problem, from a client computing system and runs a problem-specific analyzer to generate additional problem-specific data. A root cause for the problem is identified along with a recovery action, based on the diagnostic data package and the additional problem-specific data. The root cause and recovery action are communicated to the client computing system.

Abstract: A computing system in a server environment receives a diagnostic data package, corresponding to a problem, from a client computing system and runs a problem-specific analyzer to generate additional problem-specific data. A root cause for the problem is identified along with a recovery action, based on the diagnostic data package and the additional problem-specific data. The recovery action indicates whether it can be performed by an end user or an administrative user. Communication with the end user and administrative user is controlled based on the recovery action.

Abstract: A computing system in a server environment receives a diagnostic data package, corresponding to a problem, from a client computing system and runs a problem-specific analyzer to generate additional problem-specific data. A root cause for the problem is identified along with a recovery action, based on the diagnostic data package and the additional problem-specific data. The root cause and recovery action are communicated to the client computing system.

Abstract: A client computing system detects when a problem is encountered with an application and identified problem-specific diagnostic data that is to be collected, given the detected problem. It also identifies one or more problem-specific test or diagnostic analyzers and executes those analyzers to generate additional data. The data that is collected and the data that is generated by the analyzers is packaged and sent to a service computing system for identifying a remedial action that can be performed to address the problem. The remedial action is received and surfaced for the user.

Abstract: Interest based navigation of communications is provided. In some examples, an application, such as a communication application, receives a communication from a source. The communication is parsed to identify an interest and a participant account associated with the communication. The communication application assigns the communication to an interest container associated with the interest and to an account container associated with the participant account. Furthermore, the communications are presented in the interest container and in the account container within a navigation user interface (UI).