Workflow - Scheduled Trigger: How Historical Data Takes Effect

Q: How does scheduled triggering work?

• Creating, updating, or restoring data will match the workflow with scheduled triggering. If conditions are met, pending tasks will be generated.

Q: What are the options when saving modified definitions?

• Select “Stop executing historical tasks after saving (Recommended). Note: All initiated tasks before the workflow modification will be terminated.” This will delete previously created scheduled tasks, requiring data updates to recreate new scheduled tasks.

• Select “Continue executing historical tasks. Note: Tasks will proceed based on their original scheduled execution times.” Existing scheduled tasks will execute but won’t follow the new rules.

picture coming soon:

Q: Do historical data take effect by default?

• Historical data won’t take effect automatically. You can use batch update scheduled tasks to retrigger workflows or perform bulk imports with data updates.

Q: Why don’t historical data take effect immediately?

• Some enterprises have massive historical datasets. Immediate activation could cause sudden system overload.

1. Schedule Type: One-Time Execution

picture coming soon:

1. Schedule Type: Recurring Execution (Daily)

picture coming soon:

1. Scheduled Trigger Rules

• If modified fields are used in the scheduled workflow, tasks will recalculate based on new values. Example: Changing the execution date from 2020-12-31 to 2021-01-01 updates the task start time to 2021-01-01.

picture coming soon:

• Time accumulation in execution calculations: For example, if execution is set for 12 hours after record creation (e.g., creation time: 2021-01-01 18:00), the system calculates execution time as 2021-01-02 06:00. Time additions may affect execution dates.

picture coming soon: