Skip to main content
Question

Can the MWM Mobile “Long running app” warning be configured or disabled?

  • October 13, 2026
  • 1 reply
  • 14 views
Do Gooder (Customer)
Forum|alt.badge.img

Has anyone run into the “Long running app” warning in MWM Mobile on iOS?

We recently had a user receive this message after MWM Mobile had been running for an extended period:

Long running app
The app has been running for more than XX hours and should be restarted. Close the app by swiping it away from recent apps, then open it again.

We originally thought this might be an iOS-generated message, but the MWM Mobile log shows:

“Clevest.Mobile.PIBL.LogicHandlers.LoginHandler - Presented long running app message”

So it appears to be coming from MWM Mobile itself.

I've looked through the Mobile CONFIG.XML and the server-side configuration settings but haven't been able to identify anything that controls the application runtime threshold.

Does anyone know whether this warning or its threshold is configurable, or if it is hard-coded into the MWM Mobile client?  Ideally, we'd like to know what the the threshold is and if it can be adjusted or the prompt disabled.

We're currently on MWM 8.4 su3

1 reply

Do Gooder (Employee)
Forum|alt.badge.img+2
  • Heidi Banda
  • Do Gooder (Employee)
  • October 13, 2026

 

Why this exists

iOS can terminate an app it detects has been running too long. To reduce those unexpected shutdowns, 8.4 SU1 added uptime checks that ask users to restart MWM Mobile on a schedule, before the OS forces the issue.

The feature can’t be turned off, but you can adjust the timings and the messages to suit your operation. We recommend keeping the limits reasonably close to the defaults, since a long-running app can cause performance issues in MWM Mobile.

If the settings do not exist in your config.xml file, the system will use the defaults.

How it works

There are two checks:

Check When it runs What happens Default Minimum
Login restart At login If the app has been running longer than the limit, the user must restart before continuing. Pressing OK closes the app. 12 hours (43200 sec) 1 hour (3600 sec)
In-use warning While the app is in use If the app has been running longer than the limit, the user is prompted to restart. This is advisory only and does not close the app. 24 hours (86400 sec) 8 hours (28800 sec)

 

Configuration

Both limits and both messages are set in config.xml:

<item>  <name>LoginRestartUptimeLimitSeconds</name>  <value>43200</value></item><item>  <name>AppRestartUptimeWarningSeconds</name>  <value>86400</value></item><item>  <name>LoginRestartUptimeMessageTemplate</name>  <value>The app has been running for more than {0} hour(s) and must be restarted. This application will be closed. Please reopen it.</value></item><item>  <name>RestartUptimeMessageTemplate</name>  <value>The app has been running for more than {0} hour(s) and should be restarted. Close the app by swiping it away from recent apps, then open it again.</value></item>
Setting Purpose
LoginRestartUptimeLimitSeconds Uptime limit checked at login
AppRestartUptimeWarningSeconds Uptime limit checked while the app is in use
LoginRestartUptimeMessageTemplate Message shown for the login check
RestartUptimeMessageTemplate Message shown for the in-use warning

In the message templates, {0} is replaced with the number of hours.

Good to know

  • These settings apply to iOS and Android only.
  • Values below the minimums aren’t supported.
  • You can reword the messages to match your organization’s language, as long as you keep {0} where the hour count should appear.

Please reach out to our support team if you would like assistance setting this up for your environment.

Terms & ConditionsAccessibility statement