[Bug] Automation Email modifier ignored: HH:mm:ss missing from Date variable

I am experiencing an issue where the time modifiers for date variables in Automations are not being fully respected. Although I have configured the variable to include the 24-hour time format, the resulting email only displays the date (YYYY-MM-DD) and completely omits the time (HH:mm:ss).

Step to Reproduce:

  1. Trigger: Set an automation to trigger when a row containing a specific keyword is created.

  2. Action: Send an email to my inbox.

  3. Variable Configuration: In the email body, I inserted the “Created Time” variable and applied the following modifiers:

    • Format: YYYY-MM-DD HH:mm:ss (24-hour)

    • Timezone: Asia/Shanghai

  4. Result: Trigger the automation.

Expected Behavior: The email should display the full timestamp, for example: 2026-04-30 23:46:18

Actual Behavior: The email only shows the date: 2026-04-30 (The hours, minutes, and seconds are entirely missing).

Thanks for the detailed report. I tested this on my end — triggered the automation and was able to get the full timestamp (HH:mm:ss) to appear correctly in the email. I also tested a few other date formats and they all came through as expected. I’ll share a screenshot of my configuration and the resulting email so you can compare — it may help narrow down where the difference is.

Hi, sharing the automation doesn’t show the details.

In the Table Trigger, the outputted ‘Created Time’ is visible in ISO 8601 UTC format, which correctly includes hours, minutes, and seconds.

However, when it comes to the HTTP Request step, even though I have applied the time modifier to the variable in the POST payload, the actual data sent still only contains the date (YYYY-MM-DD) and excludes the time. It seems the modifier is being ignored or stripped during the HTTP execution step.

Additionally, please consider relaxing the restrictions on image attachments in the community forum. Currently, I am limited to uploading only one screenshot per post; any additional images have to be shared via external links in the replies.

Got it, already reproduce it.

I have some feedback to share, but here’s the catch: my English is still “loading,” so I’m currently relying on my AI sidekick to translate everything for me. :robot:

I’ve noticed most discussions here are in English. Is it okay if I post in Simplified Chinese, or should I stick to this “AI-powered English” to make sure the team can read it?

Your AI-powered English comes through just fine — and posting in English means the whole community can follow along too!