`ConstraintValidationFailed` different on Free vs Professional instance

Neo4j Graph Platform Aura & Cloud
1

Our Free instance hits an error:

Neo.ClientError.Schema.ConstraintValidationFailed
Node(312) already exists with label `profile` and property `id` = 'marcus'

node is id already exists

On our Professional Instance creating a profile node with id that already exists is no problems and works correctly.

Debug Attempts

SHOW CONSTRAINTS WHERE type = 'UNIQUENESS'

returns the same list in both instances and has nothing related to uniqueness of profiles.

Any ideas what is causing this?

2

Do you get a result back in your free version when querying for those conditions:

match(n:profile{id:'marcus'}) return n
3

Yes:

In Free: I receive a single profile node
In Production: I receive five profile nodes (correct behavior, as they have unique namespaces in the label)

The labels are

labels: ['profile', 'namespaceA']