Skip to main content

Limitations

This page describes the limitations of using the AI-native Development Support Feature. For definitions of each term, refer to the Glossary.

  • Staging ID naming constraints: The staging ID must be specified using only alphanumeric characters, hyphens (-), and underscores (_), with a length of 1 to 100 characters.
  • Only the latest deployment's assets are active: Only the latest single deployment is ever active in a staging. When you deploy again, the old assets are automatically disabled (undeployed) and replaced.
  • Undeploy is only possible in the STAGED state: Only an active (STAGED) deployment can be undeployed.
  • Staging deletion cannot be undone: When you delete a staging, all related deployments, operation history, owners, and transferred assets are also deleted. This operation cannot be undone.
  • Switching is per login session: A staging switch only takes effect for the login session of the person who operated it. It does not affect other users' environments.
  • The list shows only stagings you are participating in: The staging list shows only the stagings you participate in as an owner.
  • You cannot remove yourself directly from owners: This is a restriction to prevent accidentally locking yourself out. If needed, ask another owner.
  • Tenant environment setup execution is applied to the real tenant: The results of setup execution are applied directly to the real tenant's database and are not isolated per staging. Also, since it does not perform version management and is executed each time, idempotency (safety even when run repeatedly) is the responsibility of the configuration file side. Execution cannot be undone. The target is the assets of the current deployment.
  • A routing's real URL can only be reached after switching: To open a real URL from the "Routing" tab, you must first switch to that staging. Links before switching flow to the normal route on the main side and do not reach the target screen.