Automated scaling services can rely on server naming conventions or specific tags to identify which instances should be scaled. When server names or tags change, the configuration (policies or rules) for automated scaling must be updated to match the new conventions. If this update is not performed, the scaling feature would fail to recognize the target servers for action. In this scenario, the automated scaling feature likely relies on specific server names or resource tags that were altered during the update, preventing it from functioning correctly. It is crucial when changing server names to also update any tags and scaling policies to reflect these changes. This ensures that services reliant on those identifiers continue to operate as expected.