Troubleshooting
Start with the guide for the feature you are using. PHPSandbox’s documentation explains supported workflows; account status, current permissions and provider readiness must be checked separately.
A feature is missing or disabled
Check the current organization, your role, the organization’s subscription and the relevant connection status. Publishing, Advanced models and task availability follow the project organization’s entitlement. A failed status request is unknown state, not proof that a feature is unavailable.
An invitation failed
Confirm that you are in a team organization, have permission to invite and have a free seat. Pending invitations count toward seat usage. Read the form error before retrying. See Organizations, billing and access.
The preview does not open
Check the web process, its logs and the primary preview port. Imported projects may need .phpsandbox/setup.json. See Previews and sharing.
GitHub needs reconnecting
Reconnect the owning connection and check its status. Repository sync and GitHub MCP tools are separate connections. See Version control and Integrations.
Publishing failed
Open Publish, inspect the build or runtime error, correct the project or provider configuration and publish changes again. Check domain verification separately from the app’s publication status. See Publishing.
I pasted a secret into chat
Rotate the exposed credential through its provider and save the replacement in the secure project or vault form. Removing a message does not rotate the credential. See Environment values and secrets.
The docs do not answer my question
Ask the agent to inspect available project and account evidence. It should say when a requested capability is undocumented instead of inventing a setting.
Import inspection rejected my branch
Read the inspection reason and verify the selected repository and branch. Correct its setup or choose an appropriate fresh template and port the work deliberately. See Create or import.
Billing checkout or credits block work
Confirm the current organization, its plan type, billing period and available credits. Personal and team plans must match the organization type, and billing actions require the appropriate role. Correct the account or plan issue before repeatedly retrying a blocked request.
A source task will not start
Check that project Automation and the source are enabled. Confirm the webhook secret for Nightwatch or Sentry and the matching tool connection when Require source connection is enabled. See Task policy.
The agent misunderstood the request
Narrow the task, state the intended outcome and add the missing evidence, such as a code selection, terminal error or screenshot. Repeating vague adjectives adds less useful context than showing the relevant problem. See Agent chat.