If the firewall fails to successfully load a config upon the first configuration attempt, this can place the VyOS firewall in an unusable state since the Jinja template will no longer consider itself `first_install`, and will attempt to delete non-existent tables (e.g. `vyos_filter`).
```
vyos@vyos# set firewall ipv4 forward filter description test
vyos@vyos# commit
[ firewall ]
Unknown firewall error detected: /run/nftables.conf:19:17-27: Error: No
such file or directory; did you mean table ‘vyos_filter’ in family ip?
delete table ip vyos_filter ^^^^^^^^^^^
/run/nftables.conf:58:18-28: Error: No such file or directory; did you
mean table ‘vyos_filter’ in family ip? delete table ip6 vyos_filter
^^^^^^^^^^^ /run/nftables.conf:96:21-31: Error: No such file or
directory; did you mean table ‘vyos_filter’ in family ip? delete table
bridge vyos_filter
[[firewall]] failed
Commit failed
```
A delete action in nftables will fail if the object doesn't exist. Destroy does the same thing, but will not fail if the table does not exists, making it the safer option when deleting tables in the Jinja2 templates.
#### Delete non-existent table:
```
vyos@vyos:~$ sudo nft delete table ip test123
Error: No such file or directory; did you mean table ‘test’ in family ip?
delete table ip test123
^^^^^^^
```
#### Destroy non-existent table:
```
vyos@vyos:~$ sudo nft destroy table ip test123
vyos@vyos:~$
```