Workflow expected behavior is not as described

[mariuszkrzaczkowski]

Discussed in https://github.com/YetiForceCompany/YetiForceCRM/discussions/16172

^{Originally posted by s2b-git June 18, 2022} So, we have this triggers like 'more than hours before' or 'less than hours before' etc. Admin designing processes understand those workflows straight forward: cron running through records checking if conditions has been met, than workflow triggers. Well, actually not and I understand it would be difficult with tens of millions of records. To trigger above mentioned (and other similar) certain record needs to be kicked (for instance edited and saved without changes, or trigger manually). It makes those workflows naming pattern ambiguous. How about adding to the workflow this certain kick somehow, I mean especially to "Only once, when all conditions are met" ? I want to add that "Execution schedule (defined time intervals)" will kick it, but how about extra large set of data? Hoping for input in this matter :-)

Have a glorious weekend!

[vovpff]

Task of topicstarter can be done by selfwritten crontask but as Marius said there could be system performance problem because big amounnt of records