Find and resolve a blocked task

Start with the action that failed and its exact error. Keep the project URL and the approximate time. The sections below separate account, AI, workspace, and publishing problems so you can follow the relevant recovery path.

I cannot create or save a project

If Rigless asks you to verify your email, open Check or resend your verification email and use the message sent to the account's mailbox. Check spam and confirm you are using the same email address you registered with. If the link has expired, request a new one.

For a project or storage limit, review the Browser limits. Archived projects and stored Browser side-conversation sessions still count. Export work you want to retain before deleting an unused project. Discarding an unneeded side question can free its session slot.

If you appear to have lost a project after switching devices, confirm the signed-in account and reopen the project from recent projects. Browser projects are saved to the account. Keep any unsynchronized local work before clearing browser data.

The agent is waiting or stopped responding

Check whether it is asking a question or waiting for a tool permission. Answer the prompt shown. In the simple Create view, answer a question and choose Continue building.

Read the usage display and the latest error before retrying:

Message	Next step
Included AI allowance exhausted	Follow the displayed reset time or select a supported provider model using your own key
Provider rate, billing, or authentication error	Check the key, account permissions, and billing with that provider
Model unavailable	Choose an available model for the project's agent
Conversation context limit	Use compaction where supported, or begin a focused task with the source and necessary decisions
Connection interrupted	Reopen the same project and check its current run state before sending the task again

Plans and provider keys explains which allowance applies. Choose your agent and model explains supported combinations. If the same error repeats after addressing its cause, keep the error for support.

The preview does not work

For a Browser project, ask the agent to check index.html and its relative file paths. A dependency-install or server command cannot run in that workspace.

For a hosted project, open Advanced → Session menu → Terminal. Read the application's startup output and check that its process is still running, the expected port is listening, and it binds to 0.0.0.0. On a phone, enter Advanced through the code icon.

Follow Preview and test your app for framework-specific examples and checks for missing assets or broken routes.

GitHub cloning or pushing fails

Open Settings and check the connected GitHub account. Confirm it has access to the repository; an organization may require additional authorization. Read the clone or push error for branch restrictions or changed access. The GitHub guide covers reviewing and opening the pull request.

Publishing fails

Open the app in Apps and inspect the release details and logs. Note the stage that failed.

Stage or symptom	Next step
Missing launch configuration	Return to the source project and let the publishing flow prepare and verify the app
Build command failure	Fix the first relevant error, missing dependency, or build-time value in the source setup
Build killed or resource ceiling reached	Inspect the output for memory or disk exhaustion; a kill signal alone does not prove which resource failed
Startup or health check failure	Check the start command, port, required production variables, and health path
App-count or allocation limit	Review the plan's available app slots and resources
Release succeeds but a feature fails	Reproduce it at the public URL and inspect application logs and production configuration

Build resources and the running app's resources are separate. Rigless can retry eligible memory or disk build failures within configured ceilings. Repeatedly publishing unchanged source will not fix a bad command or missing configuration.

Keep the last working release while diagnosing an update. Hosted release history provides rollback controls within plan limits; Free keeps one current static release. Publishing explains updates and configuration.

I need to recover or retrieve my work

Use Export and run your code to save current source. For Git history, use the repository and confirm recent changes were pushed. Copy useful side answers into the main conversation before closing the page; side questions are temporary.

If you still need help, email support@rigless.ai with the project or app URL, what you did, the exact error, its time, and whether you used Browser or hosted compute. Include the selected agent and model for an AI failure. Leave out passwords, API keys, and private customer data.