We have a workflow that is getting started by Forms. There is a retrieve variable activity at the beginning of the workflow to grab the values that are needed later on in the workflow. One instance of the workflow terminated because of a value that was retrieved from the Forms instance. This also suspended the Forms instance. We edited the Forms instance variable to be the correct value and retried the Forms instance. It sent the previous value to Workflow instead of the corrected value. Is this by design?
This issue has been addressed with Forms 11 Update 3, Forms will send the latest process variables values to Workflow when workflow side doesn't specify the ID of the submission.
This is the correct behavior as Workflow retrieves form submissions, not variable values. The correction on the Forms side updates the variables, but does not modify the submission.
But I can see how this wouldn't be the expected behavior. We'll see what we can do.
We got complains about this behavior from other customers as well for self-hosted Forms, while it will always use the latest value when retry workflow service task from Cloud. We plan to update the behavior of self-hosted Forms to match the Cloud.