Troubleshooting and FAQs

The console says why it refused, in one sentence. Find the message below: what it means and what to do. Where a message holds a name or a number, it shows here as ….

Quotas and limits

Message	What it means	How to fix it
The project's daily quota of … tasks and job runs is used up	The project made its daily cap of task creations, job runs and task retries today (UTC). Nothing was added; scheduled runs are skipped (Skipped (daily quota)).	Wait for the next UTC day (Usage says when), or ask an admin to raise the cap.
The project's daily quota of … tasks and job runs has room for … more today; the file has … tasks	A file of tasks counts as one: the day has room for some of its tasks but not all, so none was made.	Make a smaller file, or wait for the next UTC day.
The daily quota of … is used up	A Force run over the project's daily cap.	As above: wait, or ask an admin to raise the cap.
The console is over a free-plan limit today; new tasks are refused until … UTC	The whole console used up one of its free limits today. Every queue is held; new tasks and job runs are refused. The Dashboard and Usage say A free-plan limit is used up: every queue is held, and new tasks and job runs are refused, until …	Wait for the time it says (00:00 UTC). Nobody can lift it early. Sign-in and the pages go on.
Too many changes this hour; try again later	You made 120 changes in the last hour. A file of tasks counts one change per 10 tasks.	Wait, then try again.
Too many queue and job reads this hour; try again later	Your hourly budget of reads of queues and jobs is spent: each page and list counts the rows it reads.	Wait, then try again. Refresh less often.
At most 10 filtered or sorted task lists an hour; try again later	A filtered or sorted task list costs more, so each person has 10 an hour. A queue also has limits of its own (This queue has had … task lists this hour; try again later).	Use the list without a filter or sort, or wait.
At most 20 exports and imports an hour; try again later	Each person may download or preview or apply a settings file 20 times an hour, together.	Wait, then try again.
At most 10 test alerts an hour for a project; try again later	The project sent 10 test alerts this hour.	Wait. Real alerts are not affected.
A project has at most 200 jobs, A project has at most 20 API keys that are not revoked; revoke one first	The project is at one of its limits: 100 queues, 200 jobs, 200 secrets, 100 service accounts, 20 keys not revoked.	Delete or revoke one you no longer need.

The queue page with a red notice at the top: Too many changes this hour; try again later — A refusal on a page action shows as a red notice at the top.

Tasks, jobs and their calls

Message	What it means	How to fix it
A task named … is in this queue, or succeeded or was deleted within the last day	Task names are unique in a queue. The queue remembers a name while the task waits, runs or is failed (7 days), and for a day after it succeeded or was deleted.	Use another name, or leave Task name empty so the queue names it. On the form, this shows at the top: scroll up to read it.
The URL is a private, local or reserved address, The URL names a local or internal host, The URL cannot be the console itself	Tasks and jobs call only public addresses: never localhost, `.local` or `.internal` names, private ranges, or the console. A host is checked again before each attempt; an attempt refused then shows Blocked URL.	Use the public address of the target.
The URL must start with http:// or https://, The URL cannot hold a user name or password; use an auth option	The URL is not one the console can call as it is.	Type a full `http://` or `https://` address; put credentials in a secret and choose it under Auth.
No … secret named … in this project	The task or job names a secret this project does not have, or one of another kind (a Bearer token for Basic auth, say).	Add the secret on Secrets, or choose one of the right kind.
The secret … has expired	The secret passed its end date. At run time an attempt fails as Auth failed: The secret … expired at … UTC.	Rotate it, and move the tasks and jobs to the new name.
The secret … may not be sent to this URL's origin (its allowedOrigins, on the Secrets page)	The URL is not at one of the secret's allowed origins, so the credential is not sent there.	Fix the URL, or add its origin with Change origins on Secrets (the secrets permission).
No service account … in this project, The service account … is disabled	The OIDC option names an account that does not exist, or is disabled.	Add it, or Enable it, on Secrets.
A token of … may not be sent to this URL's origin (its allowedOrigins, on the Secrets page), The audience is not at one of …'s allowed origins, The audience must be at the URL's own origin	The service account's tokens may go only to its allowed origins, and the audience must be at the URL's own origin.	Fix the URL or the audience, or the account's origins.
No such queue, No such job, No such task	It is not in this project: it was deleted, the link is old, or the name is mistyped.	Open it again from its list, and check the project in the picker.
No such project, and the page No such project: That project does not exist, or you have no access to it.	The project does not exist, or you have no permission on it.	Choose a project from the picker, or ask an admin for access.
The task is running or already done	The action does not fit the task's state now.	Refresh. A running task finishes on its own.

Forms and files

Message	What it means	How to fix it
A message beside a field, such as name is 1 to 63 lower-case letters, digits and dashes, starting with a letter, maxDispatchesPerSecond is more than 0 and at most 500 or minBackoff is at most maxBackoff	The console checked the form and refused that field. The message names the field as the console knows it.	Change the field and send the form again. On a job, the step that holds the field opens.
Check these: at the top of a form	Messages the console could not place beside a field.	Read each line; fix and send again.
… is not a JSON file.	The file you chose is not valid JSON. Nothing was sent.	Fix the file in a text editor, or start again from Download a sample.
Choose a file of tasks first., Choose a settings file first.	You clicked Create tasks or Preview with no file chosen.	Choose the file, then click again.
A path before the message, such as `tasks.1.url` url is required: an http:// or https:// URL	A mistake in a file names its place: `tasks.0` is the first task, `tasks.1` the second, then the field. In a settings file: `settings.queues.2.maxAttempts`. Nothing was made.	Fix that place in the file and try again.
Not a field of this request	A file holds a field the console does not know.	Take it out, or compare with the sample.

The Create queue form with red messages under two fields — Field messages beside their fields.

The From a file panel with a red message and the path tasks.1.url — A file's mistake, with its place in the file.

Signing in

Message	What it means	How to fix it
Wrong email, password or code	The break-glass sign-in was refused. It is the same for every reason: a wrong email, a wrong password, a wrong or used code, and a locked account.	Check all three and use a fresh code (or an unused backup code). After 5 wrong tries from your address it is locked for you for 15 minutes; after 50 from all addresses, for everyone. Wait 15 minutes, or reset the password.
Too many sign-in attempts from this address; try again later	Too many sign-in tries from your address in 15 minutes.	Wait, then try again.
Wrong code: enter the code your authenticator shows now, The enrolment has expired; sign in again	During the authenticator set-up: the code was wrong, or the set-up waited too long.	Type the code the app shows now; or sign in again to start the set-up again.
Not invited: ask an admin to invite you, This account is disabled	The Google account is not a console user, or an admin disabled it.	Ask an admin to invite you (or enable you), then accept from the link.
This invitation has expired or was used; ask an admin to send it again	The invitation link is older than 7 days, or was used.	Ask the admin to resend it.
This passkey was not accepted	A passkey sign-in was refused. It is the same for every reason.	Try another passkey, or sign in with Google and add a new one.
Sign in with Google (or your password) first: a passkey works for 30 days after one	Your last sign-in with Google or the password was more than 30 days ago.	Sign in with Google (or the password) once; passkeys work again.
The passkey sign-in has expired; start again, No passkey was used: it was cancelled, timed out, or this device has none for the console.	The passkey prompt was cancelled or waited too long, or this device holds no passkey for the console.	Click Sign in with a passkey again, on a device that holds one.
Sign in again to add or remove a passkey	Adding or removing a passkey needs a sign-in in the last 15 minutes.	Sign out, sign in, and try again.
Sign in first	Your session ended: 12 hours without use, 7 days at most, or a sign-out on every device.	Sign in again.

The Admin sign-in card with the red message Wrong email, password or code above the fields — The break-glass refusal: one message for every reason.

Pages and banners

Message	What it means	How to fix it
The banner Maintenance is on for …: its queues and jobs are held with who switched it on and when	The project's maintenance switch is on: nothing is sent, new tasks are accepted and wait, scheduled job runs are skipped. Maintenance is on for the whole console: every queue and job is held is the console's switch.	If the deploy is over, click Resume dispatch on Projects (the pause permission), or ask who switched it on.
Something went wrong on this page. Reload and try again.	The page met an error that was not a message from the console, such as a lost connection.	Reload the page. If it goes on, tell an admin: the console may be down.
The page The console could not load	The console did not answer when the page opened.	Click Try again, or Back to sign-in.
Only an admin may do this	The action is for admins.	Ask an admin.
A maintenance switch changes at most once every 10 seconds; try again shortly	The switch was changed less than 10 seconds ago.	Wait a moment, then try again.
No alert channel is set	A test alert with no email address and no chat saved.	Add a channel on Alerts and click Save, then test.
Mail is off: set the MAIL_* settings to send invitations	The console's mail is not set up, so it cannot send invitations (or reset links, or summaries).	Ask the console's owner to set up its mail.

FAQs

Why is a button missing?

Your permissions. A page shows only the buttons you may use in that project: no create permission, no Create queue; no delete, no Delete. The table in Finding your way lists them. Ask an admin for more.
The state. A running queue offers Pause, a paused one Resume; Run now is for a queued task, Retry for a failed one; the default queue cannot be deleted.
No project chosen. Queues, Jobs and the project settings show once you choose a project in the picker.
Admins only. People, Audit log, Create project, Set the cap and Hold every project.
The browser. Sign in with a passkey and Add a passkey show only where the browser can use passkeys.

Why did my task not run yet?

The queue is paused: its chip says Paused. Click Resume.
The queue is held: its chip says Held until … UTC (daily limit), near a free-plan limit for a low-priority queue, or every queue while the console is over one. It goes on by itself at that time.
Maintenance is on: the banner says so. Nothing is sent until someone resumes dispatch.
Its schedule time is later: the ETA column says when it is due.
It is waiting to retry: its state says Retrying (attempt …); the queue's backoff sets the wait.
The daily quota is used up: a retry waits for the next UTC day.
The queue's rate: Max dispatches per second and Max concurrent dispatches limit how many start at once.

Why did my job not run?

It is Paused: no Next run. Click Resume.
Its run says Skipped, and why: Skipped (maintenance), Skipped (quiet hours), Skipped (still running) (the run before had not ended) or Skipped (daily quota).
The project's quiet hours hold jobs: it runs once when the window ends, or skips the time, as the job says.
A job runs within a minute of its time, in its own time zone: check the Frequency and the zone under it.

How long are things kept?

What	How long
A failed task	7 days in its queue
A task's name, after it succeeded or was deleted	1 day (a new task cannot take it meanwhile)
A task's headers and body	Until the task is done
Attempts of a task	Its newest 10, at most 7 days
A job's runs	7 days
An uptime check's results	Its last 100
A queue's metrics	Per minute for 2 days, per hour for 30 days
The audit log	400 days
An invitation link	7 days, and one use
A password reset link	30 minutes, and one try
A session	12 hours without use, 7 days at most
A daily summary's unsubscribe link	60 days
An API key or secret	Until its end date, if it has one, or until it is revoked or deleted

Where do I get help?

Ask an admin of your console, such as the one who invited you. They can see the audit log, change your access and raise a daily cap.
Admins: the Dashboard's Cron tile, Usage and the audit log are the first places to look; the console's owner has its runbook for what breaks.
How it all works: How it works, Limits and free plan, Security and access, For apps and Task files.

Cloud Console user manual, from the console as it is on main. The pictures are of a local copy with a made-up project, shop, and a made-up admin. 22 Oct 2026.