Perspective Audible Alarm - weird behavior on clients

Hello! I am seeing weird behavior with an audible alarm playback that hopefully someone can help with. We have an Audio component within a Flex Container on the Navigation bar, linked to a .wav file and all of that is working perfect. I am using the isAlarmActiveFiltered expression in the Play binding to only be active for High or Critical Unack alarms.

In Designer, I can see that my logic is working correctly, showing True or False on Play if there is an Active alarm or not. In our Production system, we have several PCs running the Perspective Client, and the audible playback is not matching the logic that I see in Designer, the alarm is either off or on depending if you manually hit the play or pause button, and not responding to the expression logic.

I loaded the Gateway backup on my local PC and verified that the audio is working for me in my browser, so I’m not sure if there is something interfering with the Production system clients or if I am missing a step somewhere.

My understanding is that you should see the icon as a ‘Play” symbol / triangle when there are no alarms, and the system will automatically play the alarm and the symbol will change to the Pause symbol, indicating the audio is being played. Is there a manual override or something that could have been enabled on the clients that needs to be disabled or something?

Are these sessions opened in regular consumer browsers? Are there any errors in the browser console? Are they totally unattended when the audio starts playing?

Not positive it's the root of the problem, but there's unavoidable restrictions on browser tabs autoplaying sound without user interaction (because a browser cannot distinguish between a Perspective session sounding a critical alarm and a crappy popup ad trying to get you to buy something).

The sessions are running in Edge browser on multiple workstations in a secure environment / no outside internet access. They have at least one workstation logged into this particular site and leave it up on a summary screen for passive monitoring. I will look into Edge settings and see if there could be any potential blockers, I’m not aware of any errors or warnings from the browser side.

I’m not sure what happened, I’m not getting the alarms to work now on my local PC anymore. When I check the binding on the audio.props.Play, the expression preview is showing either True or False like it should, however, the value is not updating in Designer preview mode unless I open the binding and hit OK. I am not sure if this is intended behavior or not, just an observation. I am stumped now, not sure what changed from yesterday on my local system or what the issue is in general.

quick update - the audible alarm seems to be working in Designer but not Chrome or Edge on the client side, and I am not able to find anything blocking the autoplay. If anyone has any ideas on what to check next it would be greatly appreciated.

Autoplay is blocked by default in most browsers. Look in the browser.

I should have mentioned I checked all the security settings and made sure auto play was enabled, added the site to the trusted sites, etc. I’m not seeing any notifications or pop up block messages, etc. it seems like the request is not getting to the browser.

Thanks,
Craig