In versions of Dynamics 365 prior to the Fall 2016 release (8.1 and prior), organizations that wanted to automate their business processes relied on a few work-arounds, most notably the need to force values on the ProcessID, StageId (active stage) or TraversedPath attributes. Frequently, these techniques would fail with either an error message or a displaying a broken process control. However, there was a small but not fully determined subset of cases where these techniques would appear to work. These techniques would not present obvious visual glitches or error messages, but would typically result in corrupt data in the database. In all of these cases, Microsoft has maintained that programmatically manipulating the business process state is not a supported scenario: neither the front-end web control or the underlying infrastructure have the necessary logic to handle stage skipping, which was not part of the original design.