Why a scan won't run
Why a scan will not run: the Run or Refresh button is disabled or a run was rejected, with the common reasons and fixes.
When Run or Refresh is disabled
If Refresh now (or the run button) is greyed out, hover it: the tooltip names the reason. Here are the common ones and how to fix each.
- The project has no prompts. There's nothing to ask yet. Add prompts, or let LumaRank draft a set for you. See Generating prompts with AI and Editing, regenerating and deleting prompts.
- You're out of refreshes this month. Manual runs use refreshes. Wait for your monthly reset, or top up. See Refreshes and how runs are billed and Buying more refreshes.
- A scan is already running. Only one scan runs at a time on your account. Let the current one finish, then start the next.
- Your role is view-only. Owners, admins and editors can run scans; viewers can't. See Inviting teammates and roles.
- Your subscription isn't active yet. A paid plan needs checkout completed before it can run scans. See Upgrading, downgrading and checkout.
- The account is paused for review. See If your account is paused for review.
When a run is rejected after you start it
- "This scan includes prompts flagged as unsafe." One or more prompts didn't pass our safety check. Edit or remove the flagged prompts and run again. See Keeping prompts genuine (acceptable use).
- A run that fails part-way shows what happened on the dashboard, tagged Action needed (something in your setup) or On our side. See Scan statuses.
If none of these apply and a run still won't start, try again in a few minutes, then contact support.