Support

Get in touch

• In-product ticket. Open a support ticket from the MIOSA dashboard. This is the fastest path for account-specific issues because it carries your tenant context.
• Email. Write to platform@miosa.ai for anything that is not tied to a live resource, such as roadmap questions or a limitation you need lifted.

What to include

A precise report resolves in one round trip. Include:

• The resource id (sandbox, computer, deployment, secret) and your tenant or workspace.
• The operation that failed and how you invoked it (SDK call, CLI command, raw request).
• A timestamp with timezone, and the request’s x-request-id header if you have it.
• The error text exactly as it came back, including the status code.
• What you already checked, such as the pending network queue or build logs.

Before you open a ticket

Many issues have a documented fix:

• Troubleshooting is the front door for sandbox, exec, preview, network, and deploy problems.
• Security troubleshooting covers secrets, OAuth, the network allowlist, and the audit log.
• miosa doctor checks your CLI version, config, endpoint, key, and clock skew in one command.

Status and changes

• Status page. The status page shows current platform health and recent incidents. Check it first if something looks broadly broken rather than scoped to your tenant.
• Changelog. The changelog lists what shipped, and Known limitations lists what has not.

Raising a limit

Concurrency, rate limits, and volume terms can be raised for a plan. Ask through the same channels and include your expected scale; see Pricing and limits for the current defaults.