I thought this is a bugs reporting channel, not one for consulting about bugs.. nvm
The workaround is understanding the bug and live with it. It still a bug..
There’s also a Custom option (maybe a new one that hasn’t been documented yet?), which allows you to set the time to run. This time shows different values in the UI than in the backend
It is a bug in Clay. The UI allows setting the time for scheduled columns, but the value is saved as GMT time, and runs in GMT.
