Skip to main content
Use the symptom and the affected operation to choose a check. If you need help, include the project, resource name, time, and displayed message; omit credentials and sensitive content.

​
A project is missing

Open the organization and project selector. Select the intended organization and clear any project search. Signing in with an Entra account does not automatically add you to every ThinkPlatform project. If the project is still absent, ask its administrator to check your organization membership and project role. See Members and permissions.

​
A canvas page has a save conflict

The message “This Canvas page was modified elsewhere. Reload the page before saving.” means another change conflicts with your edit. Copy any unsaved text somewhere safe first, then reload the page, compare the current content, and reapply the needed change. Wait for Saved, navigate away and reopen or reload the page to verify it. See View and edit a canvas.

​
Uploaded vector files are not searchable yet

Open DB → Vector, select the store, and inspect its file list and indexer status and latest run information. An upload and an indexer run are separate: a file can appear before indexing completes. If the last run reports failures, use the displayed details to investigate the source and ask the search-service administrator to check the indexer. Do not repeatedly upload the same files while the result is uncertain. See Tables and vector stores.

​
Sandbox is unavailable

In the workspace creation form, inspect Runtime provider. If Azure Container Apps Sandbox is disabled or the form says Sandbox is unavailable, the deployment has not reported it ready. Ask a global administrator to prepare and verify the organization Sandbox infrastructure. If the form says it could not check readiness, resolve that check with the administrator; Azure Container Apps may remain available as another provider. See Operate agent workspaces.

​
A flow times out or its outcome is unclear

A timeout does not establish that every step failed. Open the flow’s result or node status, then inspect any external destination the flow could have changed. Record the run details and ask the responsible operator to check the target if its state is unclear. Retry only after determining whether the earlier run took effect, especially for writes or notifications. See Run a flow and inspect results. For terminal-specific problems, see CLI troubleshooting. For an unresolved issue, use Contact support and preserve its receipt or uncertain submission ID before leaving the form.