You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a recipe fails for any reason, right now you need to start over the entire process. Filling in the chosen recipe, database options and other variables as well as setting the location of the server data. I would like to suggest to be able to choose between starting over and just going back 1 step in case you mistyped something in the variables for instance.
Use Case
Well right now I ran into a recipe that was poorly configured, and used a database file with a hardcoded databasename instead of respecting the database configuration. My database user didn't have access to that database, and thus the recipe failed. Following this I had to redo the whole process. (And yeah in this case, definitely the recipe maker's fault)
But let's take a simpler use case. You have a recipe with a variable that determines something somewhere in the recipe, be it a download or a special set up or something, if you mistype what you needed to put it in fails and you have to redo the whole process. Instead it would be much easier to go back 1 step, fix your mistake, and rerun the recipe.
Proposed Solution
Add a button to go back 1 step next to the "Cancel and Return to Setup" button.
Additional Info
How it looks now when something fails:
The text was updated successfully, but these errors were encountered:
Scope
Web
Feature Description
When a recipe fails for any reason, right now you need to start over the entire process. Filling in the chosen recipe, database options and other variables as well as setting the location of the server data. I would like to suggest to be able to choose between starting over and just going back 1 step in case you mistyped something in the variables for instance.
Use Case
Well right now I ran into a recipe that was poorly configured, and used a database file with a hardcoded databasename instead of respecting the database configuration. My database user didn't have access to that database, and thus the recipe failed. Following this I had to redo the whole process. (And yeah in this case, definitely the recipe maker's fault)
But let's take a simpler use case. You have a recipe with a variable that determines something somewhere in the recipe, be it a download or a special set up or something, if you mistype what you needed to put it in fails and you have to redo the whole process. Instead it would be much easier to go back 1 step, fix your mistake, and rerun the recipe.
Proposed Solution
Add a button to go back 1 step next to the "Cancel and Return to Setup" button.
Additional Info
How it looks now when something fails:
The text was updated successfully, but these errors were encountered: