Thanks for the response Greg! I’m not sure I follow though; I can’t see a context variable that would do this?
g
Greg Roche
09/10/2021, 8:18 AM
Ah yeah I guess using context only solves half the problem (this gives you the parameter values for the current run, but not the default parameter values for the flow). I think you would be able to get the flow's default values with a GraphQL query to Server/Cloud. Alternatively you could restructure your flow a bit so that the default parameter values are stored in a variable which is then passed to the relevant task
k
Kevin Kho
09/10/2021, 2:05 PM
Hey @Michael, I don’t think this can be done, unless you explicitly query the GraphQL API like Greg mentioned, and then compare it with the value during runtime.
m
Michael
09/10/2021, 2:06 PM
Thanks both! I think this would have been hacky anyway, so probably a good thing I was forced to reshuffle some things