Workflow Wait for condition activity does not proceed at the expected due dateIssue The Wait for condition workflow activity does not transition forward at the expected time when it depends on the Due date field. Release All Cause The Wait for condition workflow activity reads the Due date value when the activity starts running. The Due date value changes after the activity starts. The value at the start was set when the record was inserted. The activity keeps using the original value and ignores the new value. Resolution This is expected base system behavior. The workflow uses the Due date value that is present when the Wait for condition activity starts running. The following example shows how this works: A parent record that the workflow is associated with is inserted. The Due date value is 2020-12-04 21:42:03 (value A).You can change the Due date field value until the workflow starts running the Wait for condition activity.If you change the Due date to a different value (value B) after the activity starts, the workflow does not use value B. The workflow keeps using value A.To resolve the issue, wait until the original Due date (value A) is reached. In this example, the workflow then progresses at 2020-12-04 21:42:03.