Description - There are actions that get blocked or error out when validating deactivated resources. The process should be smart enough to know if a resource is deactivated and remove that resource from the field rather than throwing an obscure error, ignoring the deactivated state, and creating a support issue. For example, when copying a project, and a resource manager on the project is deactivated, the copy fails at the end with an error saying the resource manager does not have a Plan account. This is meaningless and difficult to troubleshoot since the UI does not indicate that an assigned resource manager is deactivated. The copy process should realize this and simply remove the resource from the target or ignore the resource from validation since it was allowed on the source project anyway.
Why is this feature important to you - The usability and error handling is not helpful and unnecessary stoppage of processes exist for situation that should be handled by code.
How would you like the feature to work - If any resource during validation is a deactivated resource, it should either remove them from the process or ignore them from validation since nothing can be done with a deactivated resource.
Current Behaviour - Tasks that validate resources stop an action due to a deactivated resource, but does not indicate that the resource is deactivated, creating a situation where it's unclear why the action failed.
