I have an autolaunched flow that sends an email alert.
If i run the flow in debug mode (the new run scenario mode) manually it works.
If i take the same data and run it in the automation mode, it throws an error.
It seems like the flow doesnt insert the record as part of the test setup so you dont get IDs. Many flows do operations based on record ID so is this a planned addition later or a bug?
#Flow
It's neither a bug nor a pending feature — by design the Email Alert action needs a real, committed record Id (that's the SObjectRowId input) to resolve the template's merge fields and the alert's recipients. Your error shows SObjectRowId = {!input_bla.Id} (null), so in that run input_bla was never saved and has no Id — which is exactly why it fails there but works when you pass a real record manually in debug. Fix: make sure the record actually exists (has an Id) before the alert runs. If it should fire after a save, build it as (or call it from) a record-triggered after-save flow and pass {!$
Record.Id}, which is always populated post-save; if the autolaunched flow receives an uncommitted record variable, create that record first with a Create Records element and use the new Id, or pass the Id of an already-saved record instead of an in-memory variable. For a quick test, just supply a valid existing record Id as the input and it will send.
