I have a workflow that is triggered on CREATE only. It works fine. But there are transactions created through bank auto-create rules that aren’t being triggered at all (even when using a UE script). So I thought I need something to pick up these missed transactions and trigger the workflow for them. I don’t want to create another scheduled workflow with the exact same actions just for this. The Lists > Mass Updates > Initiate Workflow (my workflow) works great for these missed transactions but I can’t schedule it to run every 15 minutes without creating multiple saved mass updates. So I thought this may have an equivalent in SuiteScript which I think is the task.WorkflowTriggerTask from the n/Task module. But it only works if I add View and Update trigger on the workflow itself. And it also doesn’t trigger the Set Field Value actions on Entry of the first WF state which is handled perfectly by the UI mass update functionality. Am I missing something?

Then its best your workflow runs in both CREATE and Update/View mode. You can always play with the context/entry points in stages.

Including the right context for the bank transactions will do the trick

We have added all the contexts possible. To be specific, these are bank transactions created from the auto-create rules

What if you have a scheduled script that runs once per day that will do a dummy update save. This will make sure that the record goes into the workflow. Your scheduled script will run on only bank transactions created during the last 24hrs.

Yeah, that's what I thought too. Thanks