Consul time parsing error for local timestamps

parsing time "2026-10-11T19:13:28": invalid format

0 reputation · 11 Jan 2020, 10:41 UTC

70.3K views0

When creating an ACL token with an expiration time specified as a local date‑time string without an offset, Consul returns the error “parsing time "2026-10-11T19:13:28": invalid format”.

The goal is to determine whether Consul can be configured to interpret such strings as local time (or UTC) instead of requiring an explicit offset or UTC format.

What configuration options, if any, exist to treat expiration timestamps as local time? If none are available, what is the recommended approach for users operating in non‑UTC time zones? Is there any plan to add a setting that allows Consul to accept offset‑less timestamps?

4,399 following

0 answers

Keep exploring this topic

ShotGrid API date/time fields: Unresolved timezone conversion behavior

ShotGrid’s REST API returns UTC timestamps without timezone offsets, while the UI auto‑converts to local time. Developers wonder if the API should expose a timezone parameter or return offset‑aware strings. What is the preferred approach for client‑side time‑zone handling?

Consul KV Idempotency Under Service Mesh Retry Rerouting

Examining the interoperability between Consul service mesh retries and KV store session idempotency, focusing on whether retryed requests preserve the session identifier and write index needed for Compare-and-Swap, or risk duplicate data.

Fixed versus adaptive suspicion multiplier in Consul's WAN gossip failure detector

Consul's gossip failure detector uses a suspicion multiplier, but whether fixed or adaptive values are optimal remains an open design question affecting detection latency and false-positive rates.

param is missing or the value is invalid: limit must be an integer – Travis CI builds endpoint pagination

Travis CI’s builds endpoint uses limit/offset for pagination, but the offset indexing, empty array behavior, and handling of total_count for private repos remain unresolved. This question explores these ambiguities and asks for clarification on how to reliably paginate large build datasets.

parsing time "2026-10-11T19:13:28": invalid format

0 answers

Your perspective belongs here.

0 question comments

Good answers start here.