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

**URL:** https://community.teable.ai/t/bug-automation-email-modifier-ignored-hhss-missing-from-date-variable/222
**Category:** Teable Discussions
**Tags:** cloud
**Created:** [April 30, 2026, 8:04am UTC](https://community.teable.ai/t/bug-automation-email-modifier-ignored-hhss-missing-from-date-variable/222 "2026-04-30T08:04:40Z")
**Posts on this page:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![OtakuSay](https://community.teable.ai/user_avatar/community.teable.ai/otakusay/32/302_2.png) [@OtakuSay](https://community.teable.ai/u/OtakuSay)
#### Post date: [April 30, 2026, 8:04am UTC](https://community.teable.ai/t/bug-automation-email-modifier-ignored-hhss-missing-from-date-variable/222/1 "2026-04-30T08:04:40Z")

</div>

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:

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).

---

<div class="post-metadata">

### Author: ![Leo](https://community.teable.ai/user_avatar/community.teable.ai/leo/32/78_2.png) [@Leo](https://community.teable.ai/u/Leo)
#### Post date: [April 30, 2026, 9:07am UTC](https://community.teable.ai/t/bug-automation-email-modifier-ignored-hhss-missing-from-date-variable/222/2 "2026-04-30T09:07:58Z")

</div>

> [@OtakuSay](#):
>
> Trigger the automation.

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.

 ![image](https://community.teable.ai/uploads/default/original/1X/ef61bd981b0944bbc2a77896371c216a3570c999.png)

 ![image](https://community.teable.ai/uploads/default/original/1X/312cb966838acaa1e245915280e35dc4b402359c.png)

---

<div class="post-metadata">

### Author: ![Leo](https://community.teable.ai/user_avatar/community.teable.ai/leo/32/78_2.png) [@Leo](https://community.teable.ai/u/Leo)
#### Post date: [April 30, 2026, 9:16am UTC](https://community.teable.ai/t/bug-automation-email-modifier-ignored-hhss-missing-from-date-variable/222/4 "2026-04-30T09:16:06Z")

</div>

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

---

<div class="post-metadata">

### Author: ![OtakuSay](https://community.teable.ai/user_avatar/community.teable.ai/otakusay/32/302_2.png) [@OtakuSay](https://community.teable.ai/u/OtakuSay)
#### Post date: [April 30, 2026, 9:17am UTC](https://community.teable.ai/t/bug-automation-email-modifier-ignored-hhss-missing-from-date-variable/222/5 "2026-04-30T09:17:07Z")

</div>

![未命名 4](https://community.teable.ai/uploads/default/original/1X/411e51de3099a0d4b15c00fd2047b136e4a3aa1a.png)

---

<div class="post-metadata">

### Author: ![OtakuSay](https://community.teable.ai/user_avatar/community.teable.ai/otakusay/32/302_2.png) [@OtakuSay](https://community.teable.ai/u/OtakuSay)
#### Post date: [April 30, 2026, 9:19am UTC](https://community.teable.ai/t/bug-automation-email-modifier-ignored-hhss-missing-from-date-variable/222/6 "2026-04-30T09:19:07Z")

</div>

![未命名 5](https://community.teable.ai/uploads/default/original/1X/871c92a9c99c181af0eed275ba59996ec2a8b601.png)

---

<div class="post-metadata">

### Author: ![OtakuSay](https://community.teable.ai/user_avatar/community.teable.ai/otakusay/32/302_2.png) [@OtakuSay](https://community.teable.ai/u/OtakuSay)
#### Post date: [April 30, 2026, 9:22am UTC](https://community.teable.ai/t/bug-automation-email-modifier-ignored-hhss-missing-from-date-variable/222/7 "2026-04-30T09:22:09Z")

</div>

![6](https://community.teable.ai/uploads/default/original/1X/8764a7c7cdf160c85ea8ed40488a6cb2393998f2.png)

---

<div class="post-metadata">

### Author: ![OtakuSay](https://community.teable.ai/user_avatar/community.teable.ai/otakusay/32/302_2.png) [@OtakuSay](https://community.teable.ai/u/OtakuSay)
#### Post date: [April 30, 2026, 9:27am UTC](https://community.teable.ai/t/bug-automation-email-modifier-ignored-hhss-missing-from-date-variable/222/8 "2026-04-30T09:27:42Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![OtakuSay](https://community.teable.ai/user_avatar/community.teable.ai/otakusay/32/302_2.png) [@OtakuSay](https://community.teable.ai/u/OtakuSay)
#### Post date: [April 30, 2026, 9:30am UTC](https://community.teable.ai/t/bug-automation-email-modifier-ignored-hhss-missing-from-date-variable/222/9 "2026-04-30T09:30:36Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![Leo](https://community.teable.ai/user_avatar/community.teable.ai/leo/32/78_2.png) [@Leo](https://community.teable.ai/u/Leo)
#### Post date: [April 30, 2026, 9:38am UTC](https://community.teable.ai/t/bug-automation-email-modifier-ignored-hhss-missing-from-date-variable/222/10 "2026-04-30T09:38:55Z")

</div>

Got it, already reproduce it.

---

<div class="post-metadata">

### Author: ![OtakuSay](https://community.teable.ai/user_avatar/community.teable.ai/otakusay/32/302_2.png) [@OtakuSay](https://community.teable.ai/u/OtakuSay)
#### Post date: [April 30, 2026, 9:45am UTC](https://community.teable.ai/t/bug-automation-email-modifier-ignored-hhss-missing-from-date-variable/222/11 "2026-04-30T09:45:30Z")

</div>

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. 🤖

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?

---

<div class="post-metadata">

### Author: ![Leo](https://community.teable.ai/user_avatar/community.teable.ai/leo/32/78_2.png) [@Leo](https://community.teable.ai/u/Leo)
#### Post date: [April 30, 2026, 9:49am UTC](https://community.teable.ai/t/bug-automation-email-modifier-ignored-hhss-missing-from-date-variable/222/12 "2026-04-30T09:49:03Z")

</div>

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