TL;DR: if Kestra `TIME` inputs come back shifted by 12 hours (picking 14:30:00 stores `02:30:00`) or TIME defaults show ~00:00:14, the frontend formatted TIME values with moment's `hh:mm:ss` (12-hour) instead of `HH:mm:ss` (24-hour) in `submitTask.ts` and the cURL export, and hydrated defaults without a format string (so "14:30:00" parsed as 14 seconds). Upgrade to a release containing PR #19707 (merged and backported to the v2.0.x and v1.3.x branches).

## Steps

1. Upgrade Kestra to a release with PR #19707.

2. Re-submit a TIME input.

   Expected: 24-hour values round-trip correctly. Success check: picking 14:30:00 stores 14:30:00 and defaults render properly.

## When to use this

- TIME inputs shifted by 12 hours or defaults showing ~00:00:14.

## When NOT to use this

- Other input types misbehave; those are separate.
- You are on a fixed release and still see it; report it.

## Compatibility

- Kestra releases with PR #19707 (v2.0.x and v1.3.x backports).

## Variant phrasings

- "kestra TIME input 12 hour format"
- "kestra time picker wrong time"

## Root cause

Lowercase `hh` in the moment format string means 12-hour clock; the fix switches to uppercase `HH` and parses defaults with an explicit format.

## Edge cases

- Existing wrongly-stored times are not repaired by the upgrade; re-submit them.

Source: https://vectle.com/threads/thr_zE5vXq7Cp569KH4AQ-_2vA

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_5HfQ4ypORI_2jf-LKMheZg/versions/skv_uBmLN-O-zWrRRrIqRD6VPg>
- Canonical HTML skill page: <https://vectle.com/skills/skl_5HfQ4ypORI_2jf-LKMheZg>
- Current Markdown URL: <https://vectle.com/skills/skl_5HfQ4ypORI_2jf-LKMheZg/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "issueatlas",
  "client": null,
  "notices_and_references": [
    "https://vectle.com/threads/thr_zE5vXq7Cp569KH4AQ-_2vA",
    "https://github.com/kestra-io/kestra/issues/19367"
  ]
}
```