Run a milestone

Troubleshooting guide

Resolve the most likely onboarding, staging, verification, review, and invoice problems.

Agency operators10 min readUpdated July 24, 2026

SOW analysis problem

  • Use a supported PDF, TXT, or Markdown file, or paste the relevant text.
  • For a scanned PDF, extract the text separately and verify it before submission.
  • Reduce the input to the milestone section rather than uploading an entire contract.
  • If AI is unavailable, use the local source-grounded draft and review every quote carefully.
  • Never weaken a criterion merely because it is difficult to verify.

Staging ownership will not verify

  1. 01
    Confirm HTTPS

    The staging origin must be a public HTTPS address.

  2. 02
    Use the exact origin

    Protocol, hostname, and port must match the staging URL entered in Greenlit.

  3. 03
    Check the ownership file

    Serve the provided token at the exact .well-known path without HTML wrappers, redirects to another origin, or authentication.

  4. 04
    Check protection rules

    Password-protected previews and platform deployment protection may block verification. Use a supported public staging route or follow the provider-specific prerequisite.

  5. 05
    Retry after deployment

    CDN propagation and cached 404 responses can delay a newly added file.

A verification run fails

SymptomLikely causeNext action
Page did not loadProtection, DNS, TLS, redirect, or unsupported originOpen the exact URL in a private browser and confirm it is publicly reachable.
Assets or interactions are missingA required cross-origin asset or script was blockedDocument the external origin and use a supported build configuration. Do not broaden access silently.
Visible success but check failedThe underlying request or expected state did not succeedInspect the observed result and fix the application rather than the Greenlit criterion.
Check cannot be mappedThe promise is subjective, external, unsafe, or unsupportedLeave it for explicit client review or verify it in the appropriate system.
Capacity messageClosed-beta browser limit reachedUse the guided sample or retry during the next capacity window. Do not repeatedly submit.

Client cannot open the review

  • Confirm the review has not expired, been revoked, or already received a final decision.
  • Confirm the client is using the intended business email and the newest invitation.
  • Send the private link and access code through separate channels.
  • Do not forward another reviewer's invitation. Revoke it and create the correct review.
  • If a corporate link scanner consumed the link, contact support with the record identifier and recipient domain.

Invoice was not created

  1. 01
    Check the review disclosure

    Confirm that an invoice plan was configured before the client review and that the reviewer saw the correct billing disclosure.

  2. 02
    Check Stripe connection

    Confirm the agency's intended Stripe account is connected and authorized.

  3. 03
    Check mode

    A test-mode invoice will not email or charge the client. Live behavior requires the separately enabled live deployment.

  4. 04
    Check the dashboard

    Use the retained invoice status and operator notifications before attempting a manual duplicate.

  5. 05
    Reconcile in Stripe

    Stripe remains the invoice and payment source of truth. Never create a second invoice until the first attempt is resolved.