In a buildscan, is there a way to distinguish a user vs filewatch triggered "runPlay" task?

What I want to do: calculate the time the first runPlay task takes to "build".

Suppose I trigger a runPlay command on my application and that i have buildscans turned on. If I make a code change and access endpoint, then a new runPlay task will be triggered with a new buildscan. Suppose I do this 5 times. This means that I have 6 different buildscans

buildscan 1 | took 2 minutes
buildscan 2 | took 2 seconds
buildscan N | took 2 seconds
buildscan 5 | took 2 seconds

The first run will take longer since most of my tasks will be out of date.
All subsequent runs runs will be quicker since most of the tasks will be "up-to-date".

Thus, is there a way, in a buildscan or other mechanism that I can distinguish the first run vs other runs?

If there was, we gather useful metrics such as how many times the runPlay was run before the user stopped the process.