Troubleshooting Beyond Projects
Start from what Beyond Projects or Workspace shows you. You cannot create a project, you have no development access, Projects cannot answer, someone changed the project, your environment did not start, the preview is unavailable, another conversation is running, or your changes conflict.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
How to use this page
Find the sentence you see and follow its checks. Every check here is a read: looking changes nothing. Nothing on this page asks you to delete a project, create a second account or repeat an action whose outcome you do not know.
I cannot create a project
New project is absent and the list says "Creating a project needs Workspace development access and a role that can create projects." Two separate things are needed. Check each in the organization panel:
| Check | If it fails |
|---|---|
| Your role is Owner, Administrator or Developer | A Viewer cannot create. Ask an Owner or Administrator of the organization to change your role in Beyond Accounts |
| Workspace development says "You can develop in Workspace in this organization." | Your role is not the problem. Read the next section |
| The Organization in the header is the one you mean | Your role and your access are per organization. Change it in the header |
Other causes:
- "No template is configured in this installation, so a project cannot be created yet." appears inside the dialog. The people who run the installation have to configure a template.
- "You do not belong to an organization yet". A project always belongs to an organization: create one or accept an invitation first.
- The work already exists in Delegate or CDN. An Owner or Administrator can register an existing project without development access.
Workspace says I do not have development access
You see one of these:
- "Workspace development is not enabled for this organization. Access is closed and is granted by Beyond: joining the waitlist, signing in or being a member does not enable it."
- "Workspace development is enabled for this organization, and you have not been selected to use it. Beyond selects each member individually."
- On a project, under Develop in Workspace: "You do not have Workspace development access in this organization."
None of them is an error, and none is fixed by signing in again, by a different role, by a new invitation or by joining a waitlist. An Owner or Administrator can tell Beyond the organization is interested; that request enables nothing by itself. Development in Workspace is closed: Beyond enables an organization and selects each of its members one by one, and both are needed. An Owner cannot do either for their own organization.
Safe checks:
- Look at the Organization in the header. Access is per organization; you may have it in another one.
- Read which sentence you have. The second one means your organization is enabled and you are not selected. The first one means nobody in your organization can develop yet.
- Check that you are still a member. If the organization is missing from the Organization selector, you were removed from it, and being selected does not help without membership.
What still works without it: seeing projects, opening them in Delegate and CDN and, with the right role, registering existing projects, renaming, archiving and restoring. Closed access to Workspace development has the whole rule.
Projects cannot answer right now
The screen says "Projects cannot answer right now" and "The service or the account authority is not answering. Nothing about your access or your projects has changed.", with Try again.
This state means one thing only: Projects, or Beyond Accounts behind it, did not answer.
- You were not signed out. When your session ends, you see "Sign in to Beyond Projects" instead.
- You were not refused. A refusal reads "You do not have permission to do that here." or "That was not found, or you do not have access to it."
- Nothing changed: no project, role or access was modified by the outage.
Choose Try again. When the service answers, you continue where you were without signing in again. If you were in the middle of creating a project, press Create project again in the same dialog: it repeats the same request and cannot create two projects. If it lasts, tell the people who run your installation the time and what you were doing.
While Projects or Accounts cannot answer, nothing is approved either. A product that cannot confirm your development access does not open a development environment until it can.
Someone changed this project
After Rename, Archive, Restore or Delete project, the screen says "Someone changed this project while you were looking at it. The current version is shown now; nothing of yours was applied."
Another person, or you in another tab, changed the project after your screen loaded it. Your action was refused as a whole, and the screen now shows the project as it is. Read it, decide whether your action still makes sense, and do it again. See the same notice explained with each action.
The environment failed to start
Workspace says "Your environment did not start" and "Failed at:" with one of the stages Authorize, Capacity, Provision, Restore, Synchronize, Start or Ready, and the service's code. The stage is the one that really failed; the stages before it read Done and the ones after it Skipped.
Choose Try again, or open the project again. Both are safe and keep your work: your files are in storage that a failed start does not remove, a working copy that holds anything is never overwritten, and a first fill from the template that fails midway is taken back completely. Your drafts and conversations are kept outside the environment.
| What you see | What it means |
|---|---|
The code NOT_ADMITTED or FORBIDDEN |
It is a refusal, not a failure of the installation. Read Workspace says I do not have development access or When you do not get in |
| Failed at: Synchronize | The working copy could not be prepared: the first fill from the template, or the project's repository. A fill that fails is taken back, so trying again starts clean |
| Any other stage | The installation could not prepare or start your container at that moment. Try again later. If it lasts, tell the people who run your installation the stage, the code and the time. Do not delete anything |
See Watch it start.
"Preview unavailable"
The panel says "The preview is unavailable while the environment is stopped". A preview runs inside your environment, and nothing starts an environment except its own person: not the preview panel, not a colleague, not a visitor. Choose Start in the header, wait for Ready, then Open preview.
If you are the visitor: the person who shared the link has to start their environment. Reloading does not start it. If the preview answers that you are not allowed in, the link was revoked or sharing was narrowed; ask for a new one.
If the environment is Ready and the preview still does not load, read the warning at the top of Preview your work and share it: no preview has yet loaded in a browser end to end, because no CDN origin serves the runtime.
"Another conversation is running"
"Another conversation is running in this environment" names the conversation. One conversation runs at a time per environment, and it is always one of your own. Your message was not sent and nothing changed. Choose Go to it, then wait for it or choose Interrupt there. See One conversation runs at a time.
Your changes conflict
Two different things are called a conflict:
| You see | Where | What to do |
|---|---|---|
| "This file changed on disk while you had unsaved text." | One file in the editor. Codex, or another of your devices, wrote the file | Your text is kept and nothing is written until you choose Compare, Keep mine or Take theirs: see When the file changed under you |
| "Conflicts with the shared branch:", or "Integration rejected. Nothing changed." | Review. Someone integrated work that touches the same lines | Nothing was changed, on your side or on the shared branch. Choose Bring in integrated work, resolve the files, then Review again and Integrate changes: see Integrate |
Neither loses work, and neither is fixed by reloading the page.
Other messages
| You see | Go to |
|---|---|
| "This installation has no recovery period configured, so projects cannot be deleted yet." | When deletion is refused |
| "The recovery period of this project has passed" | Restore |
| In Workspace: "Workspace development is not enabled for you here", "Your role does not allow this", "This project is not available to you", "Workspace cannot be reached" or "Your session ended" | When you do not get in |
| In Workspace: "Your development access was revoked." or another banner that says nothing is being written | If your access ends while you work |
| "Drafts not synchronized on this device yet" | Drafts follow you |
| An entry without Open: "Not configured in this installation." or "Not available while the project is archived or deleted." | When an entry has no Open button |
| "Organization management is not configured in this installation." | What Projects shows |
| Return to Projects is missing in Beyond Accounts | Manage members and come back |
| In a Delegate connected to Beyond Projects: "Nothing to open here", or a refusal that names Beyond Projects | Use Delegate with a Beyond project |
| In CDN: Pending confirmation, or a message about the project of an application | The applications of a Beyond project |
If your symptom is not here
Start from the troubleshooting index, or search for the exact words of the message.