Workaround for Unsupported Experimental Code Columns in Scheduled Workflows

Hi Glide Community,

I’m encountering this error in my scheduled workflow:

:police_car_light: “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 ?

Thanks!

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.

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.

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.

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!

Can you explain more about how this is currently calculated?

Table: Email-Template

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.

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.

2 Likes

Yes! This solution worked! Thank you Darren!

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.