oh. feature request. When creating DFCs it would be nice to have like a commit function. So when deploying it would spin up and you could look at the data comming, and when everything looks good, you commit.. As of now when doing testing i end up with alot of crap history for the DFCs.. Another way to do this for testing, if going all in would be to have a separate DFC-test function where you deploy and the saved data goes to a separate table in the DB for testing, which perhaps store data for 7 days or whatever, and when you are happy with the DFC you could mark it as ready for production and it would automatically be moved from testing to production and the data will be saved to the correct DB.. you could perhaps also have the option to push the test data to the production DB to not loose any data.