Yeah this is definitely a problem, though arguably it could already happen. Not sure on the best way to solve this, but I would assume the application would have to handle this in an error scenario, by reattempting and checking for existence of nodes.

The Lock mechanism already does something similar to this - it uses a guid when creating an ephemeral sequential node that is used across requests, so it can identify if it succeeded but got an error response.