When something will not start

You pressed the button and nothing started. Instead there is a card with one sentence in it. Almost every refusal in unpitch is specific: the app knows why it said no, nothing was created, nothing was charged. The messages group by what they complain about.

The draft itself

Run in the Quality Check panel is dimmed for exactly one reason, and the line under it says which: Write something first — there is nothing to check yet. Simulate on a blank draft raises the same complaint as a card: Add some text before running this.

Three more refusals are about its shape.

• This document is too large or malformed to check. Trim it and try again. One message is capped at 10,000 characters, a whole document at 50,000.
• This sequence is too long, with Simulations support up to five message steps. Shorten this sequence and try again. Its one action, Edit sequence, closes the panel over your draft. Single messages have no step cap.
• This document changed since you started. Reload it, then run the check again. The saved document moved underneath the request, usually because it is open elsewhere.

Cost and allowance

Quality Check is metered as counts, Simulation in credits.

• You’ve reached your check limit for now. Try again later. The organisation's included checks are used up for this window.
• Too many checks in a row. Try again shortly. A short burst limit, not the monthly one; a few minutes clears it.
• Your included checks just ran out. Review the updated cost, then try again. The click was free when you opened the panel and became paid before it was admitted. Read the new figure under Run, then press again.
• You need more credits to run this check., and for Simulation, Not enough credits with This simulation needs 10 credits. Open Billing to review the balance or ask your organization owner for help.
• The price changed. Review the updated cost, then try again. Simulation's version is headed Review the price. Neither offers a retry: read the new cost first.

Two facts prevent a false alarm. Included checks are counted per organisation, not per person, so a colleague can spend them. And they run against two windows at once, monthly and short rolling, which is why Billing's can run right now number can be far smaller than the number left this month. Reset times there are in UTC.

Your plan, your account, your role

• This check isn’t available on your plan yet., and for Simulation, Simulation is unavailable with Simulation isn’t available right now. You can review this reader and return when it becomes available.
• Billing is updating, Simulation is paused and Balance needs attention each block a run before it starts and open Billing in a new tab, so the draft is not torn down.
• In the account menu, a balance labelled On hold shows a figure but will not be spent yet. No credits allocated yet and Balance unavailable — refresh to try again are two further states. None of the three means zero.
• Only the organisation owner can change the plan or manage billing. Everyone else sees it read-only. Nor is there a self-serve upgrade: To move to a different plan, cancel the current one first, then subscribe to the new one.
• New purchases are paused while we sort out a billing question on this account. Your current plan is not affected. The reason is never shown.

Personas and research

A Standard persona is instant and works on every plan. Research builds carry the limits.

• Research builds are on paid plans. Without research on your plan, Start research and Create this role are not disabled: they open an upsell dialog, so they look live until pressed.
• A research build is already running in this workspace — wait for it to finish. One at a time.
• Daily research limit reached — try again tomorrow. Ten per workspace per rolling 24 hours.
• Research is not available right now — try again later. A deployment state, not a plan one.
• This workspace hit its persona limit. (500) and This workspace hit its custom role limit. (100).

With two tabs open, a create or research start can also return Your active workspace changed elsewhere. Nothing was applied, and this screen has been refreshed. Nothing was made in the wrong workspace.

When the app cannot tell whether it started

One pair of messages looks alike and means opposite things.

Couldn’t start the check is certainty: it comes with No job was created., so pressing Run again is safe.

Couldn’t confirm the check started is not. The request went out and the answer was lost, so a job may exist: We couldn’t confirm whether the check started. It may already exist. Re-run safely reconciles the same saved text. Simulation behaves the same way. Press Try again with the draft and reader unchanged and it reconnects to that run. Change either and it starts a new one for 10 credits.