Expressions randomly deleting and moving around in standard new view in portal

[megamax34]

Severity

P3 - Medium (Minor functionality affected)

Describe the Bug with repro steps

I am in a standard logic app workflow in the new view.
I edit something and save and publish.
I rerun a previous run and the workflow fails because a tracked property reference was changed without me doing it.
I did not change the track property and it caused the workflow to fail.

I have noticed this in one of my conditions in the workflow as well. We noticed regression and investigated and saw that the entire expression was removed even though no one removed it. We verified that what we had locally in the repo was different than what was there.

Unfortunately I cant pin point exactly how this happened but it is concerning that logic is being dropped or replaced with a random expression.

No one else was in there editing either. I will add to it when I see it happen again.

Here is the error

here was it working just minutes before, no changes where made to this action, let alone the tracked properties.

What type of Logic App Is this happening in?

Standard (Portal)

Are you experiencing a regression?

No response

Which operating system are you using?

Windows

Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg

Yes

Workflow JSON

na

Screenshots or Videos

No response

Environment

Session ID
42b681bd1d054116b5cd534e8f0bd2be
Azure EMA version
2.60514.1.18
Designer version
5.961.17
Runtime version
1.170.37

edge

Additional context

No response

[rllyy97]

This is really strange, I'm not sure what would cause an expression to change like this just from what I know about the project, but I do agree this is concerning.
@megamax34 What change did you make to the workflow before you said the issue happened?
Also for the two instances you're mentioning, were they both recent?
If you do see it again please let us know.

[megamax34]

One happened today, that's the one I was able to get screenshots of.
The other one I mentioned happened Monday I believe, not 100% sure on that date though but definitely in the last couple business days.

For the one today I don't remember doing anything too drastic maybe a slight change to an action then published it. I didn't change the action in question at all and since it's a tracked property it can only really reference itself so it's not like I changed another action and the reference got lost.
It's weird that when it changed it referenced a variable. I was doing some testing with the business and made a small change, re-ran the test data and all the runs failed on that tracked property reference. In the future I'll try my best to get better reproducible steps I realize this isn't the best to go off of, but since it happened twice recently I wanted to report it.

[rllyy97]

@megamax34 I appreciate you reporting this still! I'll keep an eye out as I'm working on other fixes
One more question, when you said it changed one of the tracked property values to be @variables('***ClientId'), was the @variables('***ClientId') value anywhere else in the workflow already? Ex. did it move / copy it from another part of your workflow?
If you have a full workflow file that might help, if you're worried about confidentiality you can send it to me directly at rileyevans@microsoft.com

[megamax34]

I do have that variable in my workflow and it is being referenced in that action in the input body.
I actually saw it happen again today, I can verify no changes where made to the workflow during that time.
Here is the action and you can see (mostly, sorry for blocking out stuff but its sensitive data)

Here is the issue happening today

here is the activity log to show there were no writes to any workflows.

[megamax34]

@rllyy97
So I think I might know what it is.
The tracked property is pulling from @action()['inputs']?['AccountID']

"trackedProperties": {
"XXXXClientID": "@action()['inputs']?['AccountID']"
}

in the inputs of the action itself is
{
"type": "Compose",
"inputs": {
"AccountID": "@variables('XXXClientId')",
........
}

It could be this relationship that is causing it to overwrite the tracked property value.

[rllyy97]

That's very helpful thank you! I will look into it right now and give an update

[jibin7jose]

Thanks for the additional details and screenshots. The relationship you found between trackedProperties and the existing @variables('XXXClientId') reference is very helpful.

I do not yet see a confirmed repro of a random rewrite in the serializer path. The most likely risk area is the tracking dictionary editor/state sync, where the UI could keep a stale local copy of tracked properties if the value changes while the panel is open.

I have pushed a fix in PR #9387 that resyncs the tracked-properties editor state and adds a regression test. If you can share a full workflow JSON or exact repro steps, that would help confirm whether this is a stale UI state issue or a true save/load mutation.

If you keep seeing it, please include:

• the exact tracked property value before and after the change
• whether the tracking section was open when the workflow was edited
• whether the workflow was reopened before the bad value appeared
• a full workflow file if possible

That should help narrow down whether this is a stale editor state issue or a true save-time mutation.