Skip to main content
This page is used to troubleshoot visibility scope, filter criteria, resource status, and authorization settings. An object being visible on a page does not necessarily mean that the current account can use it in the creation form.

​
Cannot Find the Create Entry Point, or the Object Is Not Visible in the List

These issues are usually related to the current viewing scope, filter criteria, or account permissions. Check them in the following order:
  1. Confirm the currently logged-in tenant and the list filter criteria selected on the page, such as region, cluster, and project group.
  2. Check whether you have opened the correct tab, such as Personal Objects, Shared Objects, or the tab for the corresponding resource type.
  3. Clear the filter criteria for name, status, owner, and so on, then search again and refresh the list.
  4. If other users can see the object, ask an administrator to confirm the current account’s role permissions, project group visibility scope, and object authorization.
Object links or IDs can only help locate objects; they do not grant permission to view or operate on them. If the project group scope does not meet expectations, see Manage project groups.

​
The Resource Pool Is Visible, but Cannot Be Selected When Creating a Form

A resource pool appearing in the resource list only indicates that the current account can view it; it does not mean that the account already has permission to use it. Before creating a workload, the resource pool status, workload type, user authorization, and quota requirements must also be met.
  1. Open the details page of the target resource pool and confirm that the resource pool is ready.
  2. Confirm that the resource pool supports the current workload type, such as a development environment, training task, or inference service.
  3. On the User Information tab, confirm that the current user has been authorized and check the personal quota.
  4. Return to the creation form and confirm that the filter criteria, including region, cluster, resource type, and instance specification, are consistent with the resource pool.
When the total quota of a resource pool is insufficient, workloads may be unable to use that resource pool even if individual quota remains available. If necessary, apply for access through Instance, or contact the resource pool administrator. For complete configuration and inspection procedures, see Managing Compute Resource Pools and Quotas.

​
The volume appears in the list, but cannot be selected when creating a task

A Volume being visible does not necessarily mean that the current workload can mount it. Focus on checking the execution location, Volume status, and directory permissions:
  1. Ensure that the workload and the Volume are located in the same region and cluster.
  2. Ensure that the Volume has been created and is in an available state.
  3. Ensure that the current account has permission to use the Volume or the target directory.
  4. If directory-level permissions are enabled for the Volume, ensure that there is a public directory, custom subdirectory, or user directory that the current user can mount.
If you have just adjusted authorization or directory rules, refresh the creation form and make your selections again. For information on creating and mounting Volumes, see Create and Use Storage Volumes. For directory authorization rules, see Configure Volume Directory-Level Permissions.