@@ -73,7 +73,7 @@ For the rest of the documentation, I'll be showing examples using different form
7373* [ Includes] ( #includes )
7474* [ Path resolution in configuration] ( #path-resolution-in-configuration )
7575* [ Run commands before, after success or after failure] ( #run-commands-before-after-success-or-after-failure )
76- * [ run before and after order during a backup] ( #run-before-and-after-order -during-a-backup )
76+ * [ order of run \-\* during a backup] ( #order-of-run- -during-a-backup )
7777* [ Warnings from restic] ( #warnings-from-restic )
7878 * [ no\- error\- on\- warning] ( #no-error-on-warning )
7979* [ Locks] ( #locks )
@@ -688,7 +688,7 @@ Additionally, for the `run-after-fail` commands, these environment variables wil
688688The commands of `run-finally` get the environment of `run-after-fail` when `run-before`, `run-after` or `restic` failed.
689689Failures in `run-finally` are logged but do not influence environment or return code.
690690
691- # # run before and after order during a backup
691+ # # order of `run-*` during a backup
692692
693693The commands will be running in this order **during a backup** :
694694- ` run-before` from the profile - if error, go to `run-after-fail`
@@ -700,6 +700,10 @@ The commands will be running in this order **during a backup**:
700700- ` run-finally` from the backup section - if error, log and continue with next
701701- ` run-finally` from the profile - if error, log and continue with next
702702
703+ Maybe it's easier to understand with a flow diagram :
704+
705+ 
706+
703707# Warnings from restic
704708
705709Until version 0.13.0, resticprofile was always considering a restic warning as an error. This will remain the **default**.
0 commit comments