Same query, which was executed at different time, provided output in diff formats/sequence.

Question

Same query, which was executed at different time, provided output in diff formats/sequence.
In case 1, the output JSON sequence was {attribute(@odata.context), values, attribute(@odata.nextLink)}
In case 2, the output JSON sequence was {attribute(@odata.context, @odata.nextLink), values}

Example:
Output sequence 1:
{"@odata.context":"https://graph.microsoft.com/v1.0/$metadata#users('xxx')/mailFolders('inbox')/messages",
"value":
[{"@odata.etag":"XXX",
"id":"YYY",
...
...
...
"flag":{"flagStatus":"notFlagged"}}],
"@odata.nextLink":"XXX"}

Output sequence 2:
{"@odata.context":"https://graph.microsoft.com/v1.0/$metadata#users('xxx')/mailFolders('Archive')/messages",
"@odata.nextLink":"XXX",
"value":[{"@odata.etag":"XXX",
"id":"YYY",
...
...
...
"flag":{"flagStatus":"notFlagged"}}]}

The Tibco BW application executing this Microsoft GraphAPI query was not changed. Also the output of sequence was auto resolved after many hours
(Our JSON2XML parse engine will only accept input in output sequence 2)

Please can you help me understand what has caused this type of behavior.
This happened on 21 Oct, 2020.