Common Problems

If something feels wrong, start simple. Do not assume the whole site is broken. Most problems fall into a small number of common cases.

If the app page loads but actions fail, refresh once and make sure you are still signed in. Then check Settings and confirm that the provider key you need is actually saved.

If the site keeps asking you to sign in, sign in again through the normal site flow and then return to the app. A stale session is one of the most common causes of odd behavior.

If a run will not start, check three things first: your sign-in state, your provider key, and whether you started from a reasonable preset.

If GitHub import is failing, test the GitHub connection itself before changing anything else. A GitHub problem does not always mean the whole run setup is wrong.

If you see an error screen on one page but other pages still work, the best next step is to refresh the page and then try a different route such as Presets or Settings. That helps you tell the difference between a page problem and an account problem.

If you are stuck and need to explain the problem to someone else, include:

• which page failed
• whether you were signed in
• whether the problem happens every time
• whether it affects one page or the whole site
• whether the run ever really started

That makes support much faster.