On the screen

What the panel says in other cases

How the console handles a file of tasks

Each step runs only if the one before it passed. Beside each step is what happens when that step refuses.

1. The page reads the fileIt reads the file as JSON and sends it unchanged. However often the button is clicked while the request runs, it sends one request.
   The file is not JSON: the page says so and sends nothing.
2. Signed in, from the console's own pageThe session, the CSRF token and the page's origin. The request counts as one change against the person's hourly budget.
   401 or 403; 429 when the person's change budget is used up.
3. Allowed in this projectThe person needs the create permission. The queue is looked up in this project only.
   403 without the create permission; 404 for a queue this project doesn't have.
4. The whole file is checked first1 to 50 tasks and 256 KB at most. Each task is checked as a single create is, unknown fields are refused, and no task name may appear twice in the file.
   400, with a message for each problem at its place in the file. Nothing is made. A body over 256 KB gets 413.
5. Secrets and service accountsEvery secret and service account the file names must exist in the project, be of the right kind and not be disabled or expired. Its URLs must be ones that secret or account may go to. Two database reads, however many tasks there are.
   400 at the task's path, for example tasks.1.auth.secret. Nothing is made.
6. The person's change budgetA file counts one change per 10 of its tasks (5 for 50), so one person makes at most 1,200 tasks an hour from the pages.
   429, "Too many changes this hour". Nothing is made.
7. The project's daily quotaThe file's tasks are counted all at once, against the cap of 5,000 a day by default.
   429, saying how much room is left today, for example "room for 12 more today; the file has 30 tasks". Nothing is made.
8. The queue adds the tasksOne request to the queue adds each task in the file's order, and an unnamed task gets a name. The change is written to the audit log as a single line.
   A name the queue still remembers is refused for that task only, and its quota unit is given back. The other tasks are made.
9. The page shows the answerThe label, the refused tasks with why, and a link back to the queue. Once tasks are made, the page clears the chosen file, so a second click cannot make the unnamed ones again.
   Made. When nothing was made, the label appears as a refusal instead.

What the file holds

A JSON object with one field, tasks: a list of 1 to 50 tasks, each with the fields of the Create a task form. This is the sample:

{
  "tasks": [
    {
      "name": "sample-task-1",
      "method": "POST",
      "url": "https://example.com/",
      "headers": { "content-type": "application/json" },
      "body": "{\"hello\":\"world\"}",
      "auth": { "kind": "none" },
      "attemptDeadline": "3m"
    },
    {
      "method": "GET",
      "url": "https://example.com/",
      "auth": { "kind": "none" }
    }
  ]
}

The answers

The sample settings file (Export and import)

1. Download a sample, and change itA setting left out takes its default; a section left out is not touched.
   The file is not JSON: the page says so and sends nothing.
2. PreviewA dry run: what would be made or changed, what is skipped and why, and which secrets and service accounts the file names that the project doesn't have.
   400 at the path in the file, for example settings.queues.0.maxAttempts.
3. ApplyShown only when the dry run allows it. Making the sample's queue and job needs the update and create permissions, and making the paused job needs pause as well.
   Made as one batch, with one line in the audit log.

On a phone, and against impatient clicks

• The From a file panel appears together with the form once it has loaded, so it never jumps down a phone's screen. It is as wide as the form.
• The file chooser's button uses the console's own style in light and dark mode.
• A refused task's long name is cut to its column and shown whole on hover.
• Only the summary line is read aloud by a screen reader; a refusal is an alert of its own.
• Double- or triple-clicking Create tasks, Preview or Apply sends one request. A test locks that in for each of them.

On main and deployed since pull request #25, after typecheck, lint and all 1,122 tests passed. It went in as three commits: CAP-159 (the plan and the API contract), CAP-160 (the sample settings file) and CAP-161 (tasks from a file). 22 Oct 2026.