Troubleshooting decision tree
Identify the affected area before changing settings.
Troubleshooting decision tree
VELORYZ Studio · Troubleshooting reference Audience: Users, support agents and maintainers Guide type: Practical Studio operations guide
Purpose
Troubleshooting decision tree should be treated as an end-to-end responsibility, not an isolated button. Start by defining what will change, who can approve it and how success will be checked. Identify the affected area before changing settings.
This guide covers identify the affected area before changing settings. Use it as an actionable practical studio operations guide: verify the current UI and any provider configuration before relying on a control in production.
Availability and responsibility
Troubleshooting must begin with the observable symptom and available logs. Do not report a provider, integration or service as functioning merely because a route or file exists in source.
Before committing time or budget, confirm who operates this workflow: the visitor, the client portal user, a Studio owner, or the delivery team. A feature described in design documentation is not automatically a public account entitlement.
Before you begin
- Exact page path, timestamp, browser/device and steps to reproduce
- Expected result, actual result and any non-sensitive error message
- Relevant project reference without private credentials
- A short list of measurable success criteria specifically for troubleshooting decision tree.
- A recovery plan if the proposed change creates a regression.
Recommended procedure
- Locate the relevant area or public route. For new projects, establish the brief at /create/; for owner-only content changes, use authenticated Studio Control at /admin. Do not assume a missing feature exists.
- Define the specific work item for Troubleshooting decision tree: capture the initial state, user intent, relevant data, permissions, expected output and what must not change.
- Follow the design and operating decisions listed below. Work in a draft, staging or reviewed project handoff where available; avoid editing live customer data experimentally.
- Review the effect with real content and realistic viewport sizes. Record any exception and obtain the appropriate approval before a public change.
- After the change, verify the public outcome rather than relying on a success message alone; preserve a reference to the reviewed version.
Topic-specific operating procedure
These steps apply to Troubleshooting decision tree. The implementation must be verified against the current Studio permissions, deployed provider connections and approved project scope.
- Start with the observable symptom and classify UI, network, API, auth, database or deployment failures.
- Check the simplest safe reproduction, then isolate whether it affects one account or all visitors.
- Use the relevant specialised troubleshooting article rather than making blind configuration changes.
- Document evidence, severity, next action and closure test.
Evidence to retain
- The original input or situation, and a clear before/after comparison.
- The reviewed version, responsible owner and acceptance record.
- Any limitation, follow-up decision, or safely reversible workaround.
Configuration and decision points
- Reproduce with the simplest possible steps and check whether the issue affects one user or all users.
- Identify whether it is a browser/UI, published content, API, authentication or provider problem.
- Test a safe mitigation and document its effect before changing production.
- Escalate with reproduction steps, impact, current status and confirmed next action.
When more than one implementation is possible, prefer the simplest approach that remains accessible, maintainable and compatible with the current source. Note any cost, licensing, privacy, ownership and performance implications before approval.
Verification checklist
- Reports contain evidence rather than speculation and identify severity.
- The fallback does not leak private information or break other flows.
- Any claimed fix is verified against the original reproduction steps.
- Recurring faults are linked to a durable documentation and regression test.
Also confirm that the result addresses the original objective: Identify the affected area before changing settings.. Review the customer-visible language, error states, navigation paths and the relevant device widths. A green build or a successful save does not by itself establish a correct production outcome.
Troubleshooting and recovery
- If user data is at risk, stop the affected action and escalate securely.
- If a page is missing, check exact route, publication and HTTP status.
- If a temporary workaround is used, document how and when to retire it.
When asking for assistance, include the exact public URL or project reference, a concise reproduction path, the expected behaviour, actual behaviour, relevant timestamps and a redacted screenshot if useful. Never include passwords, access tokens or private customer records.
Related reading
- [Editor is slow or unresponsive](/docs/studio/troubleshooting/editor-performance/)
- [Elements cannot be selected or moved](/docs/studio/troubleshooting/selection-drag-drop/)
- [AI generation failed](/docs/studio/troubleshooting/ai-failure/)
- [All VELORYZ documentation](/docs/)
- [Studio documentation](/docs/studio/)
- [Help Centre](/help/studio/)
- [/contact/](/contact/)
- [/docs/troubleshooting/](/docs/troubleshooting/)
Operational note
This article describes the Studio workflow and its acceptance criteria. Where a self-service control is not available, the action is coordinated with the Studio team rather than silently represented as automated.
