If I put a SQL statement into an ExecuteSQL processor along the lines of: SELECT * FROM foo WHERE thedate >= '2016-01-01'
and I build a flow that does something with that data, I'f found if I leave the ExecuteSQL processor running, it will continually run the query, resulting in lots of duplicate data. What is the proper way to handle something that would be sort of a one time event? Right now, I'm just setting a long run schedule time and making sure I turn the step off after it finishes the first run. -Daniel
