I told you that Akeeba Backup 10.3.6 is already doing dependency graph analysis. See \Akeeba\Engine\Dump\Native\Mysql::getTablesToBackup(). As you can see, views are added as dependency graph entities using \Akeeba\Engine\Dump\Native\MySQL\ListEntitiesTrait::getTablesViewCollection(). The entire dependency graph is resolved using \Akeeba\Engine\Dump\Dependencies\Resolver.
This will fail if there are circular references. When A depends on B, B depends on C, and C depends on A there is no resolution to the dependency graph. You will end up with an unresolved dependency which might fail at restoration time.
It will also fail if INFORMATION_SCHEMA does not return accurate information about your dependencies. See \Akeeba\Engine\Dump\Native\MySQL\ListEntitiesTrait::resolveDependencies. In your case, if the VIEW_TABLE_USAGE view does not return all dependent tables as TABLE_NAME columns we cannot possibly know there is a table dependency for that view.
If accessing INFORMATION_SCHEMA is not possible at all, we fall back to an alternate view dependency analyzer, see \Akeeba\Engine\Dump\Native\MySQL\ListEntitiesTrait::getViewDependencies. This uses a third party SQL lexer/parser library (greenlion/php-sql-parser). However, this parser can and will be confused with some syntax that valid MySQL but not well supported in it. Again, this will only happen if your database server is thoroughly broken, refusing access to a feature that's supposed to be a given.
If you have excluded tables but not the views that depend on them you are creating a broken backup. You want us to restore views which depend on tables you do not include in the backup. This is not prevented because there's a valid use case: partial backups; restoring them does indeed assume the tables missing from the backup do exist on the target server you are restoring to.
In older versions of Akeeba Backup you could also disable dependency tracking. This was removed long before 10.3.6, the version you are claiming to be using. If you actually took the backup with an older version of Akeeba Backup you may have indeed disabled dependency tracking, scoring a self-inflicted issue.
If any of these issues WHICH ACTUALLY HAVE NOTHING TO DO WITH ME AND MY CODE have occurred, the dependency resolution fails. In this case, you get a database dump, probably not in the “right” order. This will create a chicken and egg issue with the views. The root cause is either a server issue I cannot reasonably defend against, or a misconfiguration on your part I can definitely not defend against in any sensible way. You need to investigate what happened on your end.
