HyperLink replaced valid Json "&&" with "%3F"

KarenLankton_Schmidt

We are using Deep linking in AGOL to launch other applications.  This generally works.  However, occasionally where the URL  incorrectly uses "%3F" instead of the correct "?" to denote a command parameter.  I have provided the resulting URL generated by AGOL on the same map within minutes of each other.  Differences are highlighted.  Has anyone seen this before?  Other differences are using "+" instead of  "%20" for spaces 

https://apps.powerapps.com/play/264e61fa-ab96-4274-9da4-0b6452a09e7a?tenantId=dd5b5d42-c0d3-4ad2-b5f1-60edb3af2771%3FObjectID%3D5&tag=DR+xyz-YY&start=1%2F28%2F2022&end=2%2F27%2F2022&activity=Financial&sitename=Milledgeville+First+United+Methodist+Church&ScreenID=1&skipAppMetadata=true

https://apps.powerapps.com/play/264e61fa-ab96-4274-9da4-0b6452a09e7a?tenantId=dd5b5d42-c0d3-4ad2-b5f1-60edb3af2771?ObjectID=5&tag=DR%20XXX-YY&start=1%2F28%2F2022&end=2%2F27%2F2022&activity=Financial&sitename=Milledgeville%20First%20United%20Methodist%20Church&ScreenID=1

KarenLankton_Schmidt

After posting I noticed it hacked off the details I wanted to show.  Here it is again with the leading part of the URL removed

We Reproduced the bug in AGOL w.r.t hyperlinks in which AGOL take the result of the hyperlink request and reprocesses it. Here is the progression. First, is the hyperlink configured in the popups configuration screen which looks like:

?ObjectID={objectid}&tag={tag}&Start={expression/expr1}&End={expression/expr2}&activity={activity}&sitename={sitename}&ScreenID=1

When the values in {} are filled in and passed to powerapps. You will notice it replaces spaces and other non valid characters for URL's

?ObjectID=4&tag=DR%20XXX-YY&Start=1%2F28%2F2022&End=2%2F27%2F2022&activity=DES&sitename=Milledgeville%20First%20United%20Methodist%20Church&ScreenID=1

This is correct. However, if I take the above value and paste it in the link, here is what it puts out.

%3FObjectID%3D4&tag=DR+xyz-YY&Start=1%2F28%2F2022&End=2%2F27%2F2022&activity=DES&sitename=Milledgeville+First+United+Methodist+Church&ScreenID=1&skipAppMetadata=true

Which is exactly what we are seeing. I'm guessing AGOL is caching the result to save processing time, but incorrectly reprocessing it (which is the bug)