Squawk troubleshooting and a listening checklist
Resolve silence, noise, missing prices, timing issues and unexpected template behavior.
No sound
Check that audio is enabled, the browser and system output are unmuted, and the master/voice/tone levels are not zero. Test a tone. If the test works, inspect market connectivity, the selected source, incoming prints, filters and enabled alert types. A quiet market need not produce alerts. Another tab owning audio prevents a second session from starting.
Tones work but speech does not
Check the voice source, installed browser voices and spoken mode. Numeric prices need browser speech. Recorded banks contain a finite set of phrases. Changing voice source or bank can stop playback so you can enable the new selection deliberately. Long announcements can suppress later speech rather than queue old prices.
Too many or too few alerts
Compare manual and automatic thresholds, active profile scope, minimum/maximum size, side filter, interval and cooldown. Increase filtering or cooldown for a quieter experience. For missing large-print alerts, check both the large-print switch and Volume alerts master switch. Clear statistics resets captured context; allow another warm-up afterward.
Timing and data gaps
The feed may deliver executions in batches. Browser scheduling and background throttling can add delay; audio is not an execution-time guarantee. Reconnection primes fresh events instead of narrating an old backlog. Missing or stale feed data cannot be repaired with a sound setting.
Still need a hand?
Get in touch with the EdgeX team.