We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.
For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.
Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.
Great news! Our team has added a new feature in October 2024 release to assist with scheduling:
Updated jobs to support CRON scheduling. This adds the following columns to the JobDefinition table:
RecurringAdvancedMode – Type: bit (stores Boolean values, 0 or 1). Constraints: NOT NULL with a default value of 0 via the constraint
RecurringCronExpression – Type: nvarchar(200) (stores up to 200 Unicode characters)
We also feel this is a need. We run into resource issues on full update jobs overnight that could be solved by having certain jobs run only during business hours.
Absolutely agree. Some changes in data only occur during business hours when those operators are on duty. I would think it would benefit Optimizely to not have unnecessary processing activity as well.
Thanks for considering Kristin
Moving this request back to future consideration, as it a partner indicated that it is still an issue that our partners are facing.
Marking as "Will not implement" because this request is out of date and obsolete.
This is very much needed.