# \#feature-flag

**URL:** https://community.tulip.co/tag/feature-flag/328.md

[Latest](https://community.tulip.co/latest.md) · [Categories](https://community.tulip.co/categories.md) · [Tags](https://community.tulip.co/tags.md)

---

## [Feature Request: Minute-Level Automation Scheduler](https://community.tulip.co/t/feature-request-minute-level-automation-scheduler/15980)

<div class="topic-metadata">

**Author:** [@sagar007](https://community.tulip.co/u/sagar007)\
**Replies:** 3\
**Last updated:** [December 28, 2025, 3:09pm UTC](https://community.tulip.co/t/feature-request-minute-level-automation-scheduler/15980 "2025-12-28T15:09:22Z")

</div>

Overview Tulip Automations currently support a minimum schedule frequency of 1 hour. While Tulip Table events (record created/updated/deleted) can trigger automations instantly, there is no equivalent backend, sub-hour s…

---

## [Different Auto-Logout Behavior in DEV vs. PROD Instances](https://community.tulip.co/t/different-auto-logout-behavior-in-dev-vs-prod-instances/12075)

<div class="topic-metadata">

**Author:** [@jmlowden](https://community.tulip.co/u/jmlowden)\
**Replies:** 3\
**Last updated:** [August 30, 2024, 5:00pm UTC](https://community.tulip.co/t/different-auto-logout-behavior-in-dev-vs-prod-instances/12075 "2024-08-30T17:00:55Z")

</div>

Apologies as I may not have the precise lingo for these items, but here goes: I have an application that uses a timer trigger to re-initalize a loop that will act on the next (up to) 100 records that require update base…