Skip to main content

Outdated destination status

How oneclick™ determines the status​

oneclick™ displays the last known status for each destination—the status from the most recent synchronization with the cloud provider. oneclick™ does not perform a permanent live query: cloud providers block continuous status queries for all VMs.

oneclick™ updates the status in two cases:

  1. Actions performed via oneclick™. Starting, stopping, or restarting a destination through the admin interface or the workspace updates the status directly in oneclick™.
  2. Status sync. A status sync actively queries the current state from the provider. You can trigger status syncs manually or schedule them via an event profile.

When the displayed status can deviate from the actual one​

If a destination's state changes outside of oneclick™—for example via the provider portal, a script, or automatic power management—oneclick™ only detects the change at the next sync. Typical cases:

  • Automatic power management stops the server overnight outside of oneclick™: in the morning, the app tile still shows the last known status ("running").
  • An admin starts the server manually in the provider portal: oneclick™ only detects this at the next sync.

Your users therefore see an outdated status in the app tile. After a manual status reload—or at the latest at the next connection attempt—the display jumps to the correct value.

When users regularly report an outdated status​

If end users repeatedly report an incorrect status in the app tile—typically in the morning after overnight shutdowns—you can set up a scheduled status sync via an event profile (action "Synchronize VM status").

Consider the load

Status syncs generate load on the oneclick™ platform and on the cloud provider. This solution is suitable for moderate machine counts—in larger environments it can lead to performance or rate-limit issues.