# Workaround for Unsupported Experimental Code Columns in Scheduled Workflows **URL:** \ **Category:** Ask for Help\ **Created:** [April 23, 2025, 11:16am UTC](https://community.glideapps.com/t/workaround-for-unsupported-experimental-code-columns-in-scheduled-workflows/81496 "2025-04-23T11:16:12Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![tj\_talusan](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/tj_talusan/32/23565_2.png) [@tj\_talusan](https://community.glideapps.com/u/tj_talusan)\ **Post date:** [April 23, 2025, 11:16am UTC](https://community.glideapps.com/t/workaround-for-unsupported-experimental-code-columns-in-scheduled-workflows/81496/1 "2025-04-23T11:16:12Z")
Hi Glide Community, I’m encountering this error in my scheduled workflow: 🚨 _“This scheduled workflow uses unsupported Experimental Code columns.”_ I’m aware that experimental code columns aren’t officially supported in scheduled workflows, but I’m wondering if anyone has found a workaround ? ![Screenshot 2025-04-23 at 7.14.41 PM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/d/c/dc9ee36a87a95712e2765b9719a3931fe1f02afe.png) Thanks! ---
**Author:** ![MaximeBaker](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/maximebaker/32/80877_2.png) [@MaximeBaker](https://community.glideapps.com/u/MaximeBaker)\ **Post date:** [April 23, 2025, 11:43am UTC](https://community.glideapps.com/t/workaround-for-unsupported-experimental-code-columns-in-scheduled-workflows/81496/2 "2025-04-23T11:43:03Z")
The only workaround I’ve found is to preprocess result that JS column would return. Then use a set column values action to copy the result of the JS column into a plain text column. You will now be able to use that text column in your scheduled workflow. ---
**Author:** ![tj\_talusan](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/tj_talusan/32/23565_2.png) [@tj\_talusan](https://community.glideapps.com/u/tj_talusan)\ **Post date:** [April 23, 2025, 12:57pm UTC](https://community.glideapps.com/t/workaround-for-unsupported-experimental-code-columns-in-scheduled-workflows/81496/3 "2025-04-23T12:57:34Z")
![Screenshot 2025-04-23 at 8.51.14 PM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/4/9/49d3e5028deb87f6fe998f127c0bb12eceed83b6.png) This is an attempt to use a if-then column to transfer the value of the lookup column which I need. But it’s not working. ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [April 23, 2025, 1:04pm UTC](https://community.glideapps.com/t/workaround-for-unsupported-experimental-code-columns-in-scheduled-workflows/81496/4 "2025-04-23T13:04:11Z")
I’m sure there will be an effective workaround, but you haven’t really supplied enough context yet to be able to provide any meaningful advice. ---
**Author:** ![tj\_talusan](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/tj_talusan/32/23565_2.png) [@tj\_talusan](https://community.glideapps.com/u/tj_talusan)\ **Post date:** [April 23, 2025, 1:26pm UTC](https://community.glideapps.com/t/workaround-for-unsupported-experimental-code-columns-in-scheduled-workflows/81496/5 "2025-04-23T13:26:13Z")
Just to add more context on my setup: I’m building a **scheduled workflow to send a sequence of emails** based on a campaign timeline. - I have two tables: 1. **leads-campaigns** – This is the main table used in the workflow. Each row represents a lead assigned to a specific campaign. 2. **email-template** – This table stores the actual email sequence (email #1, email #2, etc.), including fields like subject, body, and send-today. Here’s what I’m trying to do: - In the email-template table, each email has a **send-today** field that marks whether that email should be sent on the current day. - Inside leads-campaigns, I use **lookup columns** to pull the appropriate email content from email-template based on that send-today filter. - The workflow checks this send-today status and sends the email accordingly. The issue is that **the send-today logic is likely being treated as experimental or computed** , so the workflow throws the “unsupported Experimental Code column” error. Thanks! ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [April 23, 2025, 1:29pm UTC](https://community.glideapps.com/t/workaround-for-unsupported-experimental-code-columns-in-scheduled-workflows/81496/6 "2025-04-23T13:29:06Z")
> [@tj\_talusan](#): > > The issue is that **the send-today logic is likely being treated as experimental or computed** , so the workflow throws the “unsupported Experimental Code column” error. Can you explain more about how this is currently calculated? ---
**Author:** ![tj\_talusan](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/tj_talusan/32/23565_2.png) [@tj\_talusan](https://community.glideapps.com/u/tj_talusan)\ **Post date:** [April 23, 2025, 1:45pm UTC](https://community.glideapps.com/t/workaround-for-unsupported-experimental-code-columns-in-scheduled-workflows/81496/7 "2025-04-23T13:45:57Z")
**Table: Email-Template** ![Screenshot 2025-04-23 at 9.45.12 PM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/2/2/229eaa6c118316b0ef754b2cba5b70628dda260e.jpeg) Adding full context with how each field in my email-template table works to help troubleshoot why it’s being flagged as using unsupported experimental code: The **Name + Step** field combines the campaign name and the email step number (e.g., “2025-06 Business Coaching Dinner-1”). This field also serves as the **relation key** to the leads-campaigns table, which allows me to pull in the correct email content for each lead. The **Event Date** is the main event date that all email steps count down toward. **Days Before Event** is a manually entered number that indicates how many days before the event a specific email should be sent. **Offset Days** is a Math column that simply multiplies the Days Before Event by -1, so I can calculate the correct offset. **Date Computed** is a JavaScript column that subtracts the Offset Days from the Event Date, giving me the target send date for each email step. **Fixed Date** is a Text-to-Date column to cleanly format the computed date. **Send Today** is an If-Then-Else column that checks if the Fixed Date matches today’s date. If it does, this field is set to true. ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [April 23, 2025, 1:58pm UTC](https://community.glideapps.com/t/workaround-for-unsupported-experimental-code-columns-in-scheduled-workflows/81496/8 "2025-04-23T13:58:10Z")
> [@tj\_talusan](#): > > **Offset Days** is a Math column that simply multiplies the Days Before Event by -1, so I can calculate the correct offset. > > **Date Computed** is a JavaScript column that subtracts the Offset Days from the Event Date, giving me the target send date for each email step. > > **Fixed Date** is a Text-to-Date column to cleanly format the computed date. My suggestion would be to replace the above three columns with a single math column: `Date - Days` - where Days is “Days Before Event”. Just as an aside, I would expect that you would be able to include all of the above logic _inside_ your workflow, negating the need for all of those columns. ---
**Author:** ![tj\_talusan](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/tj_talusan/32/23565_2.png) [@tj\_talusan](https://community.glideapps.com/u/tj_talusan)\ **Post date:** [April 23, 2025, 2:05pm UTC](https://community.glideapps.com/t/workaround-for-unsupported-experimental-code-columns-in-scheduled-workflows/81496/9 "2025-04-23T14:05:10Z")
Yes! This solution worked! Thank you Darren! ---
**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\ **Post date:** [April 30, 2025, 2:05pm UTC](https://community.glideapps.com/t/workaround-for-unsupported-experimental-code-columns-in-scheduled-workflows/81496/10 "2025-04-30T14:05:33Z")
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.