How does the workflow in AOW get started if its not part of the scheduler? how does it fire to then build the list of beans that need to have the workflow run on them as I am wanting to build cascading workflows, so one inserting record will fire two new records being created in different modules, each of which will then fire 6 different records being inserted elsewhere. I can get one layer to work, but thought that the action of merely SAVING the record fired everything related but apparently not as the cascades arent working.
Hi,
I tested this locally, albeit not to the extent of creating 2 records then 12 records, but it worked on my end at the extent that i tested.
The version that I tested this on is v7.4.3
I have attached a screenshot of one of the Workflows i used to do this.
On your workflows, You will likely need to set “Run on: New Records”
As this means workflow will fire on a newly created record, rather than one being saved.
and set a condition line similar to what I have. (i.e, Check if a field equals itself)
This is because there is occasionally an issue with workflow if there are no conditions to check on, so making a condition that should always fire will resolve it
Although, The extent that you wish to use cascading workflows may cause a Timeout.
If so, you can change your php.ini file to the following values:
Set post_max_size to at least 60MB
Set upload_max_filesize settings to at least 60MB
Set max_input_time to a large number
Set memory_limit to 256MB
Set max_execution_time to a larger number.
And restart your Apache/IIS service.
Thanks so much for this John, I tried to install 7.4.3 yesterday morning but it breaks all my custom code on every custom module I have 
so I wont be able to run on this version.
I managed to get some cascades working also using the scheduler but now I am getting duplicate records so I am working through trying to find why. I did manage to create a custom action also that creates repeating records in the underlying tables i.e. the parent record has a value of 5, to it creates 5 subrecords with a numerator number. I also added in the ability to have formulae in the proposed values that perform simple math and string replacement etc based on embedded {{$created_by}} type variable names,