Skip to main content

channel_name_invalid

HTTP 422 · code: "channel_name_invalid" · type: https://docs.formfeed.dev/errors/channel-name-invalid

The name of a release channel in the path of a channel endpoint is malformed or reserved. channel repeats the name. Nothing was changed.

Example​

{
"type": "https://docs.formfeed.dev/errors/channel-name-invalid",
"title": "Invalid channel name",
"status": 422,
"detail": "\"Staging\" is not a channel name: 1 to 32 lowercase letters, digits and dashes, starting with a letter; latest and draft are reserved",
"code": "channel_name_invalid",
"channel": "Staging",
"request_id": "req_4b7c1e9a2f3d4c5b8a6e7f9012"
}

Common causes​

  • PUT, DELETE, promote or rollback on /templates/{id}/channels/{name} with uppercase letters, spaces, underscores or a leading digit in the name.
  • A name longer than 32 characters.
  • The reserved names latest and draft, which already mean something as a render's version.

On renders and GET /templates/{id}/versions/{name}, a malformed name answers invalid_request instead.

How to fix it​

  • Use 1 to 32 lowercase letters, digits and dashes, starting with a letter: staging, beta, customer-a.
  • published is the built-in channel: move it with PUT, but it cannot be deleted (a DELETE answers invalid_request). See Release channels.

Retry?​

No. The same name gets the same answer; correct it first.