I noticed that Xano has an “Error Logs” tab where it’s possible to configure a trigger based on logged errors, which is very useful for handling and reacting to runtime issues. However, I also noticed that when this trigger is created from within the Error Logs section, it does not appear in the main “Triggers” tab where all other platform triggers are listed.
From a usability and consistency standpoint, this feels a bit confusing, because it creates the impression that the trigger exists in isolation and is not part of the overall triggers system. It would be more intuitive if error log triggers were also visible in the Triggers tab alongside the others, so that all automation logic could be managed and reviewed in one place. This would make it easier to audit, maintain, and understand all active triggers in a project without having to check multiple sections of the interface.
FA