In a scheduled task, are the conditionals checked at startup of the whole task or when the action set starts?

Question

My scheduled task works like this (these are my action sets)

• Condition(s): Account is expired and home drive exists
• Action The user's home directory gets archived

• Condition(s): Account is expired and mailbox exists
• Action: The user's mailbox gets archived

• Condition(s): A powershell script checks, if the home-archive (file path) exists
• Action: The user's home will be deleted

• Condition(s): A powershell script checks, if the pst (file path) exists
• Action: The user's account gets deleted

My Problem is

The powershell conditionals don't work as expected. I have to start a second run of the whole task to get them working.

I have the apprehension that the variable Context.ConditionIsMet gets declared at the startup/beginning of the whole task, so it gets be set to false since the archive files do not exist at that time.

• Is that true?

• How can i get the conditionals to get be checked at the runtime of the action set?

• I do not want to split the scheduled task into two!

Thanks in avance!

Answer 1

Hello,

Is that true?

All conditions in all actions sets are checked at the same time before running a scheduled task for an object. This behaviour is by design an cannot be changed.

How can i get the conditionals to get be checked at the runtime of the action set?

Unfortunately, there is no possibility to check conditions based on actions performed in previous sets.

Comments

Hi and thanks for your fast reply. Is it then possible to trigger a followup task by the scheduled one. I don't find any hint about that.

---

Hello,

It is possible to use a business rule (e.g. triggering After updating a user). They only trigger directly when a certain operation is performed over an object in the specified scope. However, in your case it does not seem to be applicable. Using separate scheduled tasks looks to be the best approach.It is possible to use a business rule. They only trigger directly when a certain operation is performed over an object in the specified scope. However, in your case it does not seem to be applicable. Using separate scheduled tasks looks to be the best approach.