> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scitix.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickly Locate Issues

> Find common issues in Siverse by symptom, and learn what information to prepare when submitting a support request.

When an issue occurs, first navigate to the relevant page based on the observed symptoms. The FAQ provides quick assessments and priority checks; for parameter descriptions, complete procedures, and in-depth troubleshooting methods, refer to the linked dedicated documentation.

## Select Issues by Symptom

| Issue | Documentation |
| - | - |
| The creation entry is not visible, the object cannot be found in the list, or a resource pool or Volume cannot be selected during creation | [Cannot Find an Entry, Resource, or Object](/siverse/faq/cannot-find-entry-resource-or-object.md) |
| A workload remains queued for a long time, an instance does not become ready, or training makes no progress | [Queued, Startup Failure, or No Progress](/siverse/faq/queued-startup-failure-or-no-progress.md) |
| Image build or pull fails, file mounting is abnormal, development environment content is lost, or SSH cannot connect | [Files, Images, and Development Environment Issues](/siverse/faq/files-images-and-development-environment-issues.md) |
| Service requests fail, traffic still cannot be handled after scaling, releases are risky, or monitoring has no data | [Service Access, Scaling, and Release Issues](/siverse/faq/service-access-scaling-and-release-issues.md) |
| Statistics are inconsistent, training needs to be resumed, or resources are about to be stopped or deleted | [Results, Recovery, and Cleanup](/siverse/faq/results-recovery-and-cleanup.md) |

## If the Issue Still Cannot Be Resolved

Before submitting a support request, please prepare the following information:

1. The object type, name or ID, and the region, cluster, and project group where the object is located.
2. The time and time zone when the issue occurred, as well as the expected and actual results.
3. The current status, event records, and redacted key logs or screenshots.
4. The image, resource specifications, mounts, commands, models, or deployment configurations modified before the issue occurred.

This information can help support personnel determine whether the issue occurred during permissions and configuration, resource scheduling, image and mounting, application startup, service traffic, or monitoring collection.

> [!WARNING]
>
> Do not provide passwords, private keys, tokens, Access Keys, or Secret Keys in support requests, logs, or screenshots.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.