I created a new node by copying an existing node's configuration. This brings up the configuration page for the new node. Before I had a chance to change and save the new configuration, it had already started the new node using the old node's configuration. This means I now had multiple executors trying to use the same account on the same host in the same directory, and they collided, resulting in failed builds.

When copying a node to create a new node, it shouldn't start the new node until after the new configuration has been saved. The new node should remain offline until either that page is saved or the node is brought online by the user.