In legacy Analytics for mobile, there was a setting to collect and cache offline transactions on the local device then send those hits once the user was online. There is no such option for this when implementing with AEP EDGE for MobileSDK. I see in Assurance that an offline device tries to send tho...

But this doesn't answer what order the rules are executed. Has no one actually read my initial question?This is for a Mobile Property in Tags(Launch)There is no ability to prioritize rules like there is in a web propertyThe ability to order the rules is useful and needed, that's why the functionalit...

Two rules can have different conditions can both qualify to be run but have competing actions. But there are scenarios where only one or the other runs. This is not uncommon at all.

Rules can have different conditions and still both qualify. For example:Rule 1: Condition - data element "stateName" is set: Action - set some XDM field to the value of stateNameRule 1: Condition - data element "stateName" is "Home": Action - modify the same XDM field to a static value of "HomePage"...

Thanks but this documentation seems to apply to Launch rules for Web Properties. This doesn't answer how Mobile Properties sequence their rules.

I am looking to order the rules themselves. Or at least understand how Launch (Tags) decides to order these rules. For example, if two rules have the same conditions but different actions, which one is executed first (or last)?

Thanks for your response but there is no priority level on rules in a Mobile Property, hence my question.It is clear that it is possible to order the actions inside of a rule, but order of execution on the rules themselves is not clear.

In Web Launch properties, it's obvious how to sequence rules per this blog post: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-platform-data/rule-component-sequencing/ba-p/362099 But in Mobile Launch Properties, when creating a rule, the Advanced Options just says, "Rule componen...