I have a task where the robot needs to read emails and perform specific actions based on the subject line.
However, for certain emails, actions should not be executed between 17:00 and 6:00.
I’m trying to figure out the best way to design the process:
Should I handle this entirely within the process flow (e.g., through conditions in the workflow)?
Or is there a way to configure time-based restrictions directly in Orchestrator (e.g., using triggers or schedules)?
I’d love to hear your suggestions on how to implement this efficiently, especially if you’ve encountered similar scenarios.
If there are steps in the process related to queue items (hopefully there are) I would do a check as I get the queue item to check what time it is and then set the defer date on the queue item to 6am.
I would specifically set the defer date rather than ignoring the queue item and closing the performer because if the queue is populated the performer will wake up every 15 or 30 minutes because of there being an item in the queue, try to process it, then stop because of the time and that is a waste of robot resources
If I store the email subject and received time as a queue item, can I then check the current time and the received time to determine whether it should be processed immediately or postponed?
Would this require a separate workflow to handle the condition checks? If it’s not the right time to process the item, how can I postpone it until 6:00 AM?
Could you share any examples or screenshots to help clarify how to implement this?
Not sure how the rest of your project is set up, so specifics around this are up to you.
I don’t have any examples as this isn’t my project so I have none to share.
If you want a more detailed answer you need to describe your process in alot more detail please.