Troubleshooting

Use this page when Superwall Agents cannot connect, an agent turn fails, or a scheduled or webhook workflow does not run.

The hosted machine is not ready

Open Settings -> Machine and check the active machine status.

If there is no machine, click Add Machine. If the machine is provisioning or reconnecting, wait for it to become ready, then refresh superwall.ai.

The agent cannot see my files

Hosted machines cannot see files on your laptop unless you upload them through chat, clone a repository, connect GitHub, or otherwise make them available to that machine.

If the file is in a repository, connect GitHub or clone the repo from Terminal. If it is a one-off file, attach it in the composer.

An automation did not run

Check:

• The automation is enabled.
• The schedule has the correct days, time, and timezone.
• The chat still exists.
• The selected machine is reachable.
• Required environment variables and integrations are configured.
• Billing is active if required.

An incoming webhook did not trigger a chat

Check:

• The webhook still exists in Settings -> Webhooks.
• You are posting to the incoming URL for the correct chat.
• The payload includes a text field.
• The selected machine is reachable.
• Billing is active if required.

An outgoing webhook is not received

Check:

• The outgoing URL is a valid http or https URL.
• Your endpoint accepts POST requests.
• Your endpoint accepts JSON.
• Your endpoint validates X-Superwall-Webhook-Secret only if you configured a secret.
• The webhook row does not show a lastError.

GitHub or Slack is disconnected

Open Integrations, reconnect the service, and start a new agent turn. Existing running turns will not automatically inherit newly connected credentials.

Environment variables are not available

Open Settings -> Environment, confirm the variable name follows shell naming rules, and save the settings. New agent turns inherit the updated environment.