Received notification from DBMS server

[yukiman76]

Getting the following error

Received notification from DBMS server: {severity: WARNING} {code: Neo.ClientNotification.Statement.UnknownPropertyKeyWarning} {category: UNRECOGNIZED} {title: The provided property key is not in the database} {description: One of the property names in your query is not available in the database, make sure you didn't misspell it or that the label is available when you run this statement in your application (the missing property name is: episodes)} {position: line: 15, column: 27, offset: 713} for query: '
                    CALL db.index.vector.queryRelationships("fact_embedding", $limit, $search_vector)
                    YIELD relationship AS rel, score
                    MATCH (n:Entity)-[r {uuid: rel.uuid}]-(m:Entity)
                    WHERE r.group_id IN $group_ids
                    RETURN
                        r.uuid AS uuid,
                        r.group_id AS group_id,
                        n.uuid AS source_node_uuid,
                        m.uuid AS target_node_uuid,
                        r.created_at AS created_at,
                        r.name AS name,
                        r.fact AS fact,
                        r.fact_embedding AS fact_embedding,
                        r.episodes AS episodes,
                        r.expired_at AS expired_at,
                        r.valid_at AS valid_at,
                        r.invalid_at AS invalid_at
                    ORDER BY score DESC
            '

When calling

results = await graphiti.search('Who was the California Attorney General?')
Using the test app

I installed from source

[danielchalef]

@yukiman76 what version of graphiti-core do you have installed?

[mobilemike]

I'm having the same problem running the Wizard of Oz example. I checked out the repo, so the version is ceb60a3

[prasmussen15]

@mobilemike Are you able to post your error message?

[mobilemike]

After elsewhere (maybe Discord?) I found someone mentioning that neo4j Desktop edition was the issue. After switching to docker hosed (Enterprise needed for the parallel backend) the problems went away.