What happens to unused assets in Orchestrator?

Unused assets in Orchestrator remain available for future use. This design choice allows organizations to retain the assets, such as credentials, queues, and other resources, even if they are not actively being utilized in automation processes. By keeping these assets available, users can easily access and repurpose them when needed without the risk of losing any previously configured settings or credentials.

This approach promotes efficiency and flexibility, as it removes the necessity to reconfigure assets that were previously in use. In contrast, while options like automatic deletion or manual archiving might seem useful for maintaining a clean inventory, these methods would limit accessibility and potentially create obstacles for developers and users who may need to reference or reuse those assets later. Additionally, the concept of assets expiring after a set period would introduce unnecessary complexity and risk the loss of important resources that could still be beneficial to the organization.