Typically actions have a 48-hour expiration unless you modify the "Ends On" date in the Execution Tab.
I've created a preset that runs between 8am and 5pm on Wednesday, but I want to kick it off on the previous Friday. If I don't manually set an "Ends-on" date it will expire before it can actually run. Is there anyway I can re-set the default expiration date of Actions?
Let me answer what I thin might be some questions posed in reply to this post:
1. Because there are several presets that are defined to run during the entire week (Sun-Sat) on different time periods (8-10am, 12-4pm, 6-10p) and so on, I want to set it up so as to make it easy for the customer to just select a Component, Take Action, Select the appropriate preset and GO!. If they have to select the "Ends On" date then the operator has to be aware of when the preset is defined to run and then count days to make sure it doesn't expire until AFTER its run date. Plus the fact that they would have to make this calculation for potentially a dozen or more actions. I'm just trying to make it as easy as possible
2. I know this can be automated using REST API, but for a moment let's assume that's not available and all you have is console commands and properties to work with.