It seems like it's no longer possible to schedule ...
# give-feedbackb
busy-horse-73824
09/08/2023, 1:25 PMIt seems like it's no longer possible to schedule experiments/experiment rules? Why has that gone? The documentation says it's possible on all rule types, including experiments
👀 1
f
future-teacher-7046
09/08/2023, 1:31 PM
I think this got missed in the recent refactor of experiment rules. We can add it back in. Long term, we want to move scheduling to the experiment itself instead of the feature rule. That way, there's a single source-of-truth for the status of the experiment and it avoids a bunch of weird edge cases (e.g. experiment is "running", but the feature rule is not active yet).
👌 1
b
busy-horse-73824
09/08/2023, 1:32 PMYeah definitely prefer it being in the experiment 🙂
busy-horse-73824
09/08/2023, 1:32 PMJust ideally want to be able to say e.g. "start at midnight" rather than "start now"
busy-horse-73824
09/08/2023, 1:32 PMalso one minor thing
busy-horse-73824
09/08/2023, 1:33 PMWe almost always run experiment targeting like this
busy-horse-73824
09/08/2023, 1:33 PMBasically because we don't just want the experiment to start at a particular time, but we only want it to affect users whose account was created from that same time
busy-horse-73824
09/08/2023, 1:34 PMIdeally it'd be good if there was a special targeting rule so we can say like
"mojo_user_created_at": { "$gte": [experiment start] }f
future-teacher-7046
09/08/2023, 1:40 PM
I'll think about ways we might be able to support a placeholder variable for experiment start date. As for "proper date comparison", we recommend using ISO dates (YYYY-MM-DDThhmmss) in UTC everywhere. Supported in almost all languages and normal string comparisons work correctly
👌 1
b
busy-horse-73824
09/08/2023, 4:18 PMWell yeah but it is hard to be certain that every use of the input will be normalized to UTC first
busy-horse-73824
09/08/2023, 4:19 PMAnd technically e.g.
+00:00Z29 Views