Skip to main content

Status Reference

This page collects the status badges and tags that appear throughout KIOPS, grouped by domain, with what to do in each state. Individual screen docs link here instead of repeating status descriptions.

Service Status​

Service status badges in the [Dashboard] and [Service Management] lists. The status cell also shows the time of the last change as relative time ("5 minutes ago").

  • Running: Running normally. No action needed.
  • Pending: Queued for build/deploy, waiting to start. Please wait.
  • Building: Building the container image. Wait until it completes.
  • Build Success (build_success): Image build finished. Proceed with Deploy next.
  • Build Failed (build_failed): An error occurred in the image build stage. Check the build log for the cause and build again.
  • Deploying: Deploying to the runtime. Wait until it completes.
  • Deploy Failed (deploy_failed): An error occurred in the runtime deploy stage. Check the target runtime connection, resources, and manifest, then deploy again.
  • Restarting: Container/Pod is restarting.
  • Stopping: The service is being stopped.
  • Failed: An error occurred during build or deploy (stage not distinguished). Check the cause with Log Monitoring and fix it.
  • Error (error): A general error state. Check the logs for the cause.
  • Stopped: Intentionally stopped. Restart if needed.
  • Registered: Registered but not deployed. Deploy is required.

Security Risk · Grade​

A summary of each service's security scan results. For the formula and details, see Security Analysis – Overview.

  • Critical: Critical vulnerability. Act immediately.
  • High: Serious vulnerability. Act promptly.
  • Medium: Security issue. Address on a planned schedule.
  • Low: Minor issue. Monitoring only.

Security score/grade: Deductions are taken from 100 by severity (Critical −20 · High −8 · Medium −3 · Low −1). The remaining score sets the grade — A (90+) · B (80–89) · C (70–79) · D (60–69) · F (below 60).

A score ceiling based on the worst severity is applied on top. This is what makes a single finding's severity dominate the grade (default values):

  • Any Critical caps the score at 70 → at most C
  • High as the worst severity caps it at 79 → at most C
  • Medium as the worst severity caps it at 89 → at most B
  • Only Low caps it at 96 → an A is still possible (99 with a single finding)

Secret findings count as High by default. What is displayed also depends on scan coverage.

  • Not assessed: no applicable area has been scanned, or every result is stale. The grade shows as "-".
  • Provisional grade: only some areas are freshly scanned. The grade is marked (provisional). Because uncovered areas carry unknown risk, each uncovered area lowers the ceiling by 10 points (for example, 1 of 5 covered → ceiling 60 = D). Scanning every area against the current code finalizes it.
  • Confirmed grade: every applicable area has been freshly scanned.
Scoring thresholds can differ per site

The ceilings above, the partial-assessment penalty, and how secret findings are treated can be adjusted by a platform administrator on the [System Administrator > Security Score Policy] screen without a redeployment. The values above are the defaults.

Runtime Health​

Build/connection status in the [Runtime Environments] list.

  • Running: The runtime is set up and working normally. No action needed.
  • Building: The runtime is being set up/installed. Wait until it completes.
  • Not Ready: Set up but currently unresponsive. Check again shortly or inspect the target's state.
  • Not Installed: Not yet set up. Proceed with runtime setup.
  • Error: Cannot connect. Check network, firewall, and credentials (Runtime Registration).
  • Unchecked: Status not yet checked. Run a connection test to refresh it.

Backup Status​

In [Backup Management], backup statuses and restore statuses use different names. The list does not refresh on its own — use [Refresh Status] to check a job in flight.

Backup​

  • Waiting: Accepted, not started yet.
  • Creating: The backup record is being created.
  • In Progress: The backup itself is running.
  • Completed: Every target was backed up.
  • Partially Failed (orange): Only part of it was backed up. The backup exists, but items are missing — click the icon next to the status to see which ones before you rely on it for a restore.
  • Failed (red): Nothing was backed up. Click the icon next to the status to see the reason. Check the target storage connection and the SSH credentials.

Restore​

  • Waiting / Restoring: Accepted, running.
  • Restored: The restore completed.
  • Partially Restored (orange): Some resources were not restored.
  • Volume Data Not Restored (orange): The resources came back but the files inside the PVC did not. This differs from "Partially Restored": no resources are missing, but the data inside them is empty. Restoring from a backup taken without PVC data ends this way.
  • Restore Failed (red): Nothing was restored. Click the icon next to the status for the reason.

Database Status​

Data Package (dump/import)​

  • ready (gray, Ready): Ready to apply.
  • applying (Applying): Application in progress. The list auto-refreshes about every 5 seconds.
  • applied (blue, Applied): Applied successfully.
  • failed (red, Failed): Error during application. Hover the status tag to see the error message.
  • deleted (displayed as Deleted): Cleaned up. Cannot apply or download.

Applied (applied) import packages are auto-cleaned after 30 days. Download locally if you need long-term retention.

Sync · Run History​

  • completed: Completed normally.
  • running: In progress.
  • pending: Waiting on schedule.
  • failed: Error occurred. Check the detailed message in run history (common causes: connection failure, permission error, schema mismatch, insufficient capacity).

Connection Status​

  • Healthy (green): Reachable.
  • Unreachable (red): Check host/port/account, firewall port opening, and remote-access permission.

Audit Log Result​

Operation result of an [Audit Log] entry.

  • DONE (displayed as "Success"): The operation completed normally.
  • PROCESSING (displayed as "In Progress"): The operation is in progress.
  • PENDING: The operation is waiting.
  • FAILED: The operation failed. Check when analyzing causes or detecting security issues.

Membership · Sign-up Status​

Organization membership status shown in [Notifications] and at login.

  • Pending (pending_approval): Waiting for the organization admin's approval. Logging in before approval shows a "pending approval" notice.
  • Approved: Registered as an organization member. Can log in and use the platform.

Pipeline Stage Notifications​

The build/deploy pipeline sends Start / Complete / Fail notifications for each stage (source · sast · build · sca · deploy · operation · dast). Fail notifications include the cause message; expand Details on the notification to see a failure-log summary. See Notifications.