Confirmation and rationale of 10-minute time window for mobile crash reporting

[pbasso]

Hello,

according to the Dynatrace documentation for mobile applications (.NET MAUI, Android and iOS), crash reports are only sent if the application is reopened within approximately 10 minutes after the crash; otherwise, the crash report is discarded.

I would like to ask for clarification on the following points:

• Is this 10-minute time window for sending mobile crash reports still confirmed in the latest Dynatrace implementation?
• What is the reason for this limitation (e.g. technical or architectural constraints related to correlation on the Dynatrace backend)?
• Is there any possibility to extend or configure this time window, or to persist crash reports for a longer period before they are dropped?

This behaviour has a significant impact on the ability to reliably collect crash data. In my context, users often work offline for several hours, which increases the likelihood of losing crash data due to this time limitation.

Thank you in advance for your support and clarification.

[Patrick_H]

• yes, the 10 minutes limit still exists in Dynatrace Classic and currently also in the new RUM experience
• main reason for this limit are correlation timeouts, writing to already closed sessions/too far into the past and timeouts for writing crash metrics and also alerting
• no this cannot be changed

as an outlook for the new RUM experience I can tell that a longer "offline" support for older (crash) events will be added in the future, so that those events can be queried (but not have an impact on alerting and metrics)