# Overnight Shift Schedules **URL:** \ **Category:** Product Suggestions\ **Tags:** feature-request\ **Created:** [December 14, 2023, 5:36pm UTC](https://community.tulip.co/t/overnight-shift-schedules/10060 "2023-12-14T17:36:05Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![alec.giljohann](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/alec.giljohann/32/6060_2.png) [@alec.giljohann](https://community.tulip.co/u/alec.giljohann)\ **Post date:** [December 14, 2023, 5:36pm UTC](https://community.tulip.co/t/overnight-shift-schedules/10060/1 "2023-12-14T17:36:05Z")
![Tulip Schedule](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/2X/1/15afc90237616e514767f8b566ce72da77451e42.png) An issue that some of our sites encountered is the lack of capability to set up a production shift that is starts on one day and ends the next (night shift). Is this feature being worked on to allow for greater flexibility to capture overnight shifts in a cleaner way other than splitting it up? (see attached) Ex. Shift Start 6:30pm - Shift End 6:30am ---
**Author:** ![kevin.kononenko](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/kevin.kononenko/32/32_2.png) [@kevin.kononenko](https://community.tulip.co/u/kevin.kononenko)\ **Post date:** [December 15, 2023, 1:46pm UTC](https://community.tulip.co/t/overnight-shift-schedules/10060/2 "2023-12-15T13:46:44Z")
Hi Alec, this is a great suggestion. We know about a number of situations that do not fit well into the current Shifts and Schedules feature. This is a good example. We are looking to do a full rebuild of the feature to capture all the variants that we know about. I don’t have a timeline for you yet. But for the time being, your approach is the best way to handle this situation. ---
**Author:** ![mellerbeck](https://avatars.discourse-cdn.com/v4/letter/m/e9bcb4/32.png) [@mellerbeck](https://community.tulip.co/u/mellerbeck)\ **Post date:** [May 9, 2024, 7:57pm UTC](https://community.tulip.co/t/overnight-shift-schedules/10060/3 "2024-05-09T19:57:16Z")
We came across this today 🙂 Is the rewrite still in the works 🙂 ---
**Author:** ![danielpomeranz](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/danielpomeranz/32/9379_2.png) [@danielpomeranz](https://community.tulip.co/u/danielpomeranz)\ **Post date:** [May 13, 2024, 5:00pm UTC](https://community.tulip.co/t/overnight-shift-schedules/10060/4 "2024-05-13T17:00:09Z")
@kevin.kononenko All a shift calculation really is is a lookup function based on day of week and time of day to some text based output. I wonder if this is really something that could just live as a custom expression ([Thread 1](https://community.tulip.co/t/custom-expression-in-expression-editor/5352), [Thread 2](https://community.tulip.co/t/use-automations-to-receive-json-or-xml-data-that-can-then-be-parsed/9700/6)) instead of trying to create an isolated, unique part of the platform. ---
**Author:** ![Richard-SNN](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/richard-snn/32/1166_2.png) [@Richard-SNN](https://community.tulip.co/u/Richard-SNN)\ **Post date:** [May 13, 2024, 8:17pm UTC](https://community.tulip.co/t/overnight-shift-schedules/10060/5 "2024-05-13T20:17:27Z")
I worked around this for machines using a Node Red flow that does the lookup from a table (in Tulip BTW) and then publishes the result to a MQTT Broker. I then pipe in in through Kepserver and map it to a machine attribute I record on state change. That way I can do all my analytics by shift which is a requirement for us. For applications I started with a connector function that returns the last 3 shifts (including the current). If I only need the current shift I just use a table aggregation. ---
**Author:** ![Beth](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/beth/32/5987_2.png) [@Beth](https://community.tulip.co/u/Beth)\ **Post date:** [May 14, 2024, 2:02pm UTC](https://community.tulip.co/t/overnight-shift-schedules/10060/6 "2024-05-14T14:02:04Z")
Thanks for your input / workaround here @Richard-SNN ! @mellerbeck @danielpomeranz @alec.giljohann - Just to be fully transparent, the rewrite on the schedules & shifts feature is likely far out due to other priorities. That being said, I think Richard’s suggestion is a good one, and perhaps another thing that may help is using Automations (Schedule a task to update a table field with the current shift) which would be more reusable than a bunch of triggers across your apps. You can actually see an example of this from @Amit in his post [Automation using expression with dates](https://community.tulip.co/t/automation-using-expression-with-dates/10973) ---
**Author:** ![Richard-SNN](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/richard-snn/32/1166_2.png) [@Richard-SNN](https://community.tulip.co/u/Richard-SNN)\ **Post date:** [May 14, 2024, 2:46pm UTC](https://community.tulip.co/t/overnight-shift-schedules/10060/7 "2024-05-14T14:46:35Z")
Thanks for the reminder! I need to reevaluate the solution once we upgrade to LTS 12.