Ran the tests on 2 records, results are below. Results are not what I was expecting- the Flow Step Request Campaign has a similar system behavior of re-issuing the campaignRunId after it's generated. API-based Request Campaign Call #1: This is the first person in the campaign, so it created a campaignRunId Flow Step-based Request Campaign #1: Incremented by 1, generated another campaignRunId API-based Request Campaign Call #2: re-used campaignRunId from 1st API call Flow Step-based Request Campaign #2: re-used campaignRunId from previous Request Campaign flow step API-based Request Campaign Call #3: Using a different test lead, re-issued original API-based campaignRunId Flow Step-based Request Campaign #3 Using a different test lead, re-issued flow step campaignRunId
... View more