A computer device includes a memory. The computer device also includes at least one processor configured to execute a process and manage the memory for the process. The processor is further configured to execute one or more program instructions associated with an application, reach control flow transfer for the one or more program instructions, unwind a call stack associated with the one or more program instructions in response to a failure to meet a target control flow, identify an offending function call, and rewrite the offending function call. The rewritten function call includes a memory operation boundary check.

Arrangements for providing API failure detection and processing are provided. In some aspects, call logs including calls made to one or more APIs as well as a response code for each call may be received and a severity for each API may be determined. For instance, an API having a third severity may be detached from an associated application to disable functionality associated with that API. If an API is assigned a second severity, additional calls may be made to the API to confirm that the API is actually failing. The results of the additional calls may be analyzed and if a sufficient number of failures are detected, an instruction to detach the API may be generated and transmitted. In some arrangements, the error causing the failure may be remedied and the API may be reattached to the application.

Disclosed are systems, methods, and articles for determining compatibility of a mobile application and operating system on a mobile device. In some aspects, a method includes receiving one or more data values from a mobile device having a mobile medical software application installed thereon, the data value(s) characterizing a version of the software application, a version of an operating system installed on the mobile device, and one or more attributes of the mobile device; determining whether the mobile medical software application is compatible with the operating system by at least comparing the received data value(s) to one or more test values in a configuration file; and sending a message to the mobile device based on the determining, the message causing the software application to operate in one or more of a normal mode, a safe mode, and a non-operational mode.

Assets are associated to a data protection policy. Configuration information is received for the data protection policy. The configuration information includes a data protection job to perform for the assets and a schedule for the data protection job. A shadow policy is generated that includes the configuration information. The data protection policy is executed. Upon detecting a failure of the data protection job for an asset, the asset is moved from the data protection policy to the shadow policy. The shadow policy is executed. Execution of the shadow policy includes calculating a base time value, adding a random time value to the base time value to obtain a wait time, and after the wait time has elapsed, retrying the data protection job.

Assets to associate to a data protection policy and configuration information for the policy is received. The configuration information includes a data protection job to perform for the assets and a schedule for the job. A shadow policy is generated including the configuration information from the data protection policy and a retry protocol. The data protection job is performed according to the schedule. A failure of the data protection job for an asset is detected. The asset is moved out of the data protection policy and into the shadow policy. The data protection job for the asset is retried according to the retry protocol in the shadow policy.

Described embodiments include methods and systems for managing client-side services. An intermediary may receive metadata from a first client device of the plurality of client devices. The metadata can include runtime characteristics of a first instance of a service that is incorporated into a client-side application or a web application. The first instance may execute on the first client device and request service data from the at least one server. The intermediary can detect an anomaly in the operation of the first instance of the service. The intermediary can identify an operation of the first instance of the service causing the detected anomaly. The intermediary can, responsive to the detected anomaly, cause delay, removal or modification of operations corresponding to the identified operation, in other instances of the service executing on the plurality of client devices.

Various embodiments provide for determining problematic components of an application that may cause user experience issues when running the application, and preemptively turning off or disabling the problematic components so that the application is rendered without the problematic component. When a component is rendered, various runtime data is produced. Such data may be logged and analyzed, and used to generate performance metrics of the component. Such performance metrics can be used to determine whether a component should be disabled. When a component is disabled, it become unavailable and will be excluded from the application when the application is rendered and/or served to a user. Thus, when an application is rendered or served, only available or enabled components are included.

Disclosed are systems, methods, and articles for determining compatibility of a mobile application and operating system on a mobile device. In some aspects, a method includes receiving one or more data values from a mobile device having a mobile medical software application installed thereon, the data value(s) characterizing a version of the software application, a version of an operating system installed on the mobile device, and one or more attributes of the mobile device; determining whether the mobile medical software application is compatible with the operating system by at least comparing the received data value(s) to one or more test values in a configuration file; and sending a message to the mobile device based on the determining, the message causing the software application to operate in one or more of a normal mode, a safe mode, and a non-operational mode.

A computer-implemented system and method detect an error in an application comprising a component having a control that is displayed in a first state on a display device. Responsive to the detecting of the error, the method comprises associating the error with the control, and, upon making this association, the method comprises automatically modifying the component at application run-time. This modification indicates that the control is no longer functional. A display operation of the component is performed where the modified component has: a) the control displayed in a second state on the component, or b) the control is removed from the component. The method may be repeated when other errors occur, and the control may be restored when the underlying error is resolved.

A scheduling scheme configuration method includes performing state verification on a plurality of operation dimensions involved in generating a scheduling scheme, and, in response to one or more of the operation dimensions being abnormal, removing the one or more abnormal operation dimensions to generate a new scheduling scheme.