Understanding Client Status Indicators

Client status indicators in the Client Manager provide at-a-glance information about the health and deployment state of each TOC client.

Understanding Client Status Indicators

Client status indicators in the Client Manager provide at-a-glance information about the health and deployment state of each TOC client. This guide explains what each status means and how to interpret the information.

Status Types

Success (Green)

Meaning: The most recent update or deployment completed successfully without errors.

Indicator: Green background or checkmark icon

What It Tells You:

  • The client is running properly on the deployed version
  • No immediate action required
  • Safe to proceed with additional updates if needed

Example Scenario: A client was updated to version 2024.11.1 last night, and the deployment completed without issues. The status shows “Success” with a green indicator.


Failed (Red)

Meaning: The most recent update or deployment encountered an error and did not complete successfully.

Indicator: Red background or error icon

What It Tells You:

  • Something went wrong during the deployment
  • The client may still be on the previous version
  • Investigation and corrective action required

Next Steps:

  1. Click View Logs to see error details
  2. Review deployment logs for specific error messages
  3. Consult with technical team to resolve the issue
  4. Retry the deployment after fixing the problem

Common Causes:

  • Network connectivity issues during deployment
  • Service dependencies unavailable
  • Configuration errors
  • Insufficient resources (disk space, memory)
  • Version incompatibility

Learn more: Viewing Deployment Logs


Updating (Blue)

Meaning: An update or deployment is currently in progress.

Indicator: Blue background or spinning progress icon

What It Tells You:

  • The client is actively being updated right now
  • Do not initiate additional updates until this completes
  • Check back in a few minutes for final status

Duration: Typical deployments take 5-15 minutes, but complex updates may take longer.

Monitoring:

  • Enable Live Updates to automatically refresh status
  • Status will change to Success or Failed when complete

What NOT to Do:

  • Do not schedule another update while status is “Updating”
  • Do not restart services manually during deployment
  • Do not navigate away if you’re monitoring the deployment

Pending (Yellow)

Meaning: An update has been scheduled but has not yet started.

Indicator: Yellow/amber background or clock icon

What It Tells You:

  • Update is queued and will begin at the scheduled time
  • No action required unless you need to cancel
  • Client is still running the previous version

Common Reasons:

  • Update scheduled for future date/time
  • Update waiting for schedule group trigger
  • Update queued behind other deployments
  • Waiting for maintenance window

What You Can Do:

  • Wait for scheduled time
  • Cancel the scheduled update if needed
  • Modify the schedule if plans change
  • Monitor the status as scheduled time approaches

Unknown (Gray)

Meaning: The system could not determine the client’s deployment status.

Indicator: Gray background or question mark icon

What It Tells You:

  • Status information is unavailable or could not be retrieved
  • This doesn’t necessarily mean something is wrong
  • May indicate communication issues with the client

Common Causes:

  • Client is temporarily offline
  • Network connectivity issues
  • Status reporting service unavailable
  • Client recently provisioned (status not yet reported)
  • Monitoring agent not responding

Next Steps:

  1. Wait a few minutes and refresh the page
  2. Check if the client is online and accessible
  3. Review network connectivity to the client
  4. If persistent, contact technical support

Important: Unknown status is different from Failed - it means we can’t get status information, not that something definitely went wrong.


Status Transitions

Understanding how statuses change helps you anticipate what comes next:

Normal Update Flow

Success → Pending → Updating → Success

A successful update cycle from start to finish.

Failed Update Flow

Success → Pending → Updating → Failed

An update was attempted but encountered errors.

Retry After Failure

Failed → Pending → Updating → Success

A failed update is retried and completes successfully.

Unknown Resolution

Unknown → Success or Failed

Status becomes available after connectivity is restored.

Date and Time Information

Along with status indicators, the Client Manager displays important timing information:

Last Run

What It Shows: The date and time of the most recent deployment attempt (successful or failed).

Use Cases:

  • Determine how recently a client was updated
  • Identify clients that haven’t been touched in a while
  • Correlate deployments with issues or changes

Example: “Last Run: 2024-11-05 10:30 AM EST”

Next Update

What It Shows: The scheduled date and time for the next deployment (if scheduled).

Use Cases:

  • See when pending updates will execute
  • Verify schedule group timing
  • Plan around scheduled maintenance

Example: “Next Update: 2024-11-06 2:00 AM EST”

Note: If no update is scheduled, this field may be empty or show ”—“

Time Zone

All dates and times are displayed in your browser’s local time zone. Coordinate with team members in different time zones accordingly.

Color Coding Quick Reference

ColorStatusAction Required
GreenSuccessNone - running smoothly
RedFailedYes - investigate and fix
BlueUpdatingWait - deployment in progress
YellowPendingNone - wait for scheduled time
GrayUnknownMaybe - check connectivity

Using Status for Decision Making

Before Scheduling Updates

Check current status:

  • Success: Safe to schedule next update
  • Failed: Fix issues before scheduling another update
  • Updating: Wait for current deployment to complete
  • Pending: Cancel existing schedule or wait for it to complete
  • Unknown: Verify client is accessible before scheduling

During Deployments

Monitor status changes:

  • Pending → Updating: Deployment has started as scheduled
  • Updating: Deployment in progress - enable live updates for real-time monitoring
  • Updating → Success: Deployment completed successfully
  • Updating → Failed: Deployment encountered errors - investigate immediately

Routine Health Checks

Use status filters to identify issues:

  • Filter by Failed to find clients needing attention
  • Filter by Unknown to identify connectivity problems
  • Filter by Success to verify update adoption rate
  • Filter by Pending to see what’s scheduled

Learn more: Filtering and Search

Status and Schedule Groups

When clients are part of schedule groups:

  • Status updates in real-time as group deployments execute
  • Multiple clients may show “Updating” simultaneously
  • Staggered deployments show mixed statuses across the group
  • Group-level status reflects collective client statuses

Learn more: Schedule Groups Overview

Troubleshooting Status Issues

Status Stuck on “Updating”

If a client shows “Updating” for longer than expected:

  1. Check deployment logs for errors or progress
  2. Verify the deployment process is still running
  3. Check for network or service issues
  4. Contact technical support if stuck for more than 30 minutes

Status Shows “Unknown” Persistently

If a client consistently shows “Unknown”:

  1. Verify the client is online and accessible
  2. Check network connectivity between Cloudscape and the client
  3. Verify monitoring agents are running on the client
  4. Review client configuration
  5. Contact technical support if issue persists

Status Not Updating After Deployment

If status doesn’t reflect a recent deployment:

  1. Refresh the page manually
  2. Enable Live Updates for automatic refresh
  3. Wait a few minutes - there may be a reporting delay
  4. Check deployment logs to verify deployment actually completed

Best Practices

  1. Check Status Before Scheduling - Always verify current status before scheduling new updates
  2. Monitor During Deployments - Use live updates to track in-progress deployments
  3. Investigate Failures Immediately - Don’t ignore red status indicators - investigate and resolve
  4. Review Unknown Status - Persistent “Unknown” status may indicate underlying issues
  5. Use Filters Strategically - Filter by status to quickly identify clients needing attention

Next Steps

Now that you understand status indicators:


For questions about specific status issues, contact your system administrator or technical support team.