Forge deploy failing for custom field with default template unchanged

I’m trying to add a custom field using forge. v10.13.6

Steps followed:

This is the manifest generated by the template (which I have not modified in any way)

modules:
  jira:customField:
    - key: custom-field-test-custom-field-ui-kit-2-hello-world
      name: custom-field-test
      description: A hello world custom field.
      type: string
      render: native
      resource: main
      edit:
        resource: edit
        render: native
        isInline: true
resources:
  - key: main
    path: src/frontend/index.jsx
  - key: edit
    path: src/frontend/edit.jsx
app:
  runtime:
    name: nodejs22.x
  id: ari:cloud:ecosystem::app/c757e4de-d93d-4e86-8156-292d1b4c54e0

forge deploy fails. This is what I see if I run with forge deploy -v.

Validation errors: {
  "validationResult": {
    "tid": "09e2a153806144bf9bd037dcd2af962d",
    "code": 400,
    "type": "UpsertEnvironmentRequestInvalidError",
    "message": "Upsert Environment Request body is invalid. Error message: jira:customField[custom-field-test-custom-field-ui-kit-2-hello-world]: must have required property 'key'"
  }
}
Validation errors: {
  "validationResult": {
    "tid": "09e2a153806144bf9bd037dcd2af962d",
    "code": 400,
    "type": "UpsertEnvironmentRequestInvalidError",
    "message": "Upsert Environment Request body is invalid. Error message: jira:customField[custom-field-test-custom-field-ui-kit-2-hello-world]: must have required property 'key'"
  }
}

I don’t know why it’s complaining about key when I can clearly see the ‘key’. Plus this is from one of the official templates.

Based on similar reports, I’d guess this was temporary? The example app works for me, at least.

Oops sorry forgot to post again. Yeah it was temporary. I woke up the next day morning and tried and it started to work lol.