Workflow failure when triggered by Mobile App (Aurena Native) – ActiveWorkOrder / Missing fields in event payload

Hello everyone,

We are facing recurring workflow errors in IFS Cloud when users perform updates from the Aurena Native Maintenance Mobile App.

Context

We have a workflow triggered on ActiveWorkOrder when a specific text field (e.g. Directive) is updated.
Everything works fine when the update is done from Aurena Web (UAT).

However, when the same action is performed from the Mobile App, the transaction fails and appears as “Failed Mobile Transaction” in the Mobility Queue.

Observations

• The workflow executes correctly from the web UI.

• The workflow fails only from the Mobile App, even for simple actions like updating a text field or adding a document.

• RowKey is enabled on the entity (ActiveWorkOrder).

• It seems the mobile event payload is incomplete (some optional fields are missing), which may cause the workflow or trigger to crash.

Questions

1. Does the Aurena Native Mobile App send partial payloads when updating an ActiveWorkOrder (only modified fields)?

2. Is it expected that optional fields (like the text field we use for the trigger) may be absent or null in the event generated by the mobile app?

3. Are there known limitations for triggering workflows on ActiveWorkOrder when the update originates from the mobile application?

4. Is there a recommended way to prevent workflow execution from Mobile App events (e.g. filtering on Context.Source or User-Agent)?

5. Are there known issues in recent IFS Cloud releases with RowKey or event generation for mobile transactions?

Goal

We need to understand how to safely trigger workflows on ActiveWorkOrder without breaking mobile transactions.

Any insight, documentation, or experience would be greatly appreciated.
Thanks in advance!