Warren Ashcroft Red Ribbon

Thanks for clarifying.

Yes, I made that comment. However, I’m raising here for discussion to understand this a bit more and how to correctly handle the scenario. The solution commented only works if we’re able to change the code, it’s not possible to change the code if it’s in a bundled script or something internal in NetSuite.

Interesting, it seems counter intuitive, since other server triggers, scripts etc... fire "Before Record Load", "After Record Submit", etc... workflows/actions as expected. The solution is as you say, but it means duplicating workflow setup, configuration and maintenance to handle both scheduled and non-scheduled contexts.

Hello, Thanks for responding, this isn't Workflow Action scripts, just builtin Workflow Actions. For example, see the attached screenshot - I'm setting the "Status" field value to "Terminated (Other)" with the condition "Keep Renewing = F And Subscription : Prevent Renewals = T And Subscription : Prevent Automated Billing…

@sklett_1107 , Did you find a solution to this? ...or could anybody else help with this, I have the same problem: A scheduled workflow is setting a field on a record, but a second workflow that's setup to run After Record Submit is not firing. If the same field is set outside the scheduled workflow, the second workflow…