Troubleshooting
When something looks wrong in Veoveo, capture enough context for an administrator or support engineer to reproduce the issue without exposing unrelated workspace data.
What To Check First
- Confirm you are in the expected workspace.
- Refresh the page and try the route again in a fresh browser tab.
- Check whether the issue affects one artifact, one workspace, one bot, or all workspaces.
- Look for visible error text, missing blobs, failed operations, or permission messages.
- Try a narrower search or filter if the issue is search-related.
Information To Include
When asking for help, include:
- workspace slug or visible workspace name
- affected route or page
- artifact, bot, or operation reference if visible
- approximate time of the problem
- visible error text
- whether the issue repeats in a fresh browser session
Do not include credentials, private tokens, unrelated workspace content, or raw provider payloads.
Common Patterns
- Missing content on an artifact often means a blob is still rendering, unavailable, or not attached to that slot.
- A bot that cannot act may lack a channel binding, available tool, or workspace permission.
- Search results that look unrelated usually need a narrower query, artifact-kind filter, or source review.
- A settings action that is not visible usually means the current user does not have the required role.
Media To Add
- Screenshot: operation timeline with a failed tool step highlighted. It helps users report bot/runtime issues precisely. Source: test workspace with a harmless failed operation.
- Table: symptom, likely area, and first check for common user issues. It helps support triage. Source: support playbook derived from public workflows.