Some users running synthetic monitors to test Citrix Cloud connections from public hives reported that a few monitors become stuck at the “Detect Workspace” prompt. This behavior was inconsistent, with some monitors seemingly configured the same way functioning normally while others encountered this issue.
The root cause was identified as related to the Citrix Workspace store’s launch method settings. The “Detect Workspace” screen corresponds to the Citrix client detection page, which is controlled on the store side rather than by Scoutbees or the synthetic monitors themselves. Specifically, when the store is configured with the “Launch virtual apps and desktops” setting set to either “Open in Citrix Workspace app” or “Let the user choose,” this page appears. On public hives, where the browser environment is fresh and does not retain prior user choices, the prompt recurs on every run, causing the monitors to stall at this screen.
To resolve this, it is necessary to verify and compare the launch settings in Citrix Cloud under Workspace Configuration (or the targeted StoreFront store). Monitors stuck on the detection prompt typically point to stores configured with “Open in CWA” or “Let the user choose,” while those that bypass the prompt are connected to stores set to “Use web browser to access apps and desktops.” Changing the store’s launch setting to “Use web browser” bypasses the native Citrix Workspace app detection page, allowing the synthetic monitors on public hives to proceed without interruption.
Before making any changes, administrators should confirm these settings by comparing the store configurations between monitors that are stuck and those that are working. This ensures an accurate diagnosis and prevents unintended side effects from changing the launch mode. Since this is a store-level configuration, it requires adjustments within the Citrix Cloud management console, specifically under Workspace Configuration. If the issue persists or if the public hive environments themselves seem problematic, submitting a support ticket for those specific hives is recommended.
For additional guidance on managing Citrix Cloud Workspace configurations and optimizing monitor setups, see the ControlUp Knowledge Base and Citrix documentation on Workspace Configuration: https://docs.controlup.com and https://docs.citrix.com/en-us/citrix-cloud/workspace-configuration.html.
Read the entire ‘Troubleshooting “Detect Workspace” Stuck Prompt for Citrix Cloud Synthetic Monitors on Public Hives’ thread below:
Hello all. We have some synthetic monitors that are testing Citrix cloud connections. We are doing this from the public hives. A few of them are getting stuck on the Detect Workspace prompt. Has anyone found a way to overcome that? It is strange because we have others that appear to be setup the same way and they are not having this issue.
that sounds like an issue with those hives, can you please open a ticket for it as the team managing them needs to look at it
Hey! That “Detect Workspace” screen sounds like the Citrix _client-detection_ page coming from the store itself, not from Scoutbees — and I think that’s actually the key to why some work and some don’t.
That screen only shows up when the store’s _”Launch virtual apps and desktops”_ setting is _Open in Citrix Workspace app_ or _Let the user choose_. Stores set to _Use web browser to access apps and desktops_ skip it entirely. On a public hive the browser is fresh every run, so there’s no “remember my choice” — if the store is set to prompt, the scout hits that wall every single time.
So my suspicion is the “same setup” ones aren’t quite the same at the _store_ level — worth comparing:
• In Citrix Cloud →_Workspace Configuration_(or StoreFront for the store the scout targets), check_Launch virtual apps and desktops_. The stuck monitors are likely pointed at stores set to_Open in CWA_/_Let user choose_; the healthy ones at_Use web browser_.
• Flipping the target store to_Use web browser_(or otherwise bypassing native detection) is the usual way to get a browser-based scout past it — no local CWA to detect.
Not 100% certain this is the whole story, so before changing anything I’d confirm by lining up a working vs. stuck monitor and comparing the store’s launch setting side by side.
I read the : _a few of them_ as few of the public hives but testing the same connection
Continue reading and comment on the thread ‘Troubleshooting “Detect Workspace” Stuck Prompt for Citrix Cloud Synthetic Monitors on Public Hives’. Not a member? Join Here!
Categories: All Archives, ControlUp Synthetic Monitoring