I have a date field called “Employee Status Changed” that automatically creates a date when the employee’s status is updated.
I created a workflow using the Time from table field trigger with the timing set to 1 day after Employee Status Changed. The workflow should send an email report.
However, the workflow never fires. I am wondering whether the automatically generated date in the Employee Status Changed field is not being accepted as a valid trigger for the workflow.
What is the data type of the “Employee Status Changed” field?
I created a Date and Time field and then a workflow that is supposed to send me an email one minute later. The workflow ran successfully, and I received the email without any issues.
This is a server-side workflow.
Since the field is being populated automatically, it may be worth checking whether the workflow engine detects that update in the same way it would a manually entered date. Recreating the workflow is a good suggestion, but you could also test with a new date field and a shorter interval (for example, a few minutes) to confirm whether the trigger itself is working. In many workflow platforms, scheduled triggers depend on how field updates are processed behind the scenes, so reviewing the platform’s Event-Driven Architecture concepts can sometimes help identify where the trigger chain is breaking. If you’re interested in broader workflow and business process automation approaches, this overview of PEGA Business Process Management also provides some useful background on how automated triggers and process orchestration typically work.