Null pointer Exception in Neo4J OGM

I am intermittently getting an NPE when I execute a query under mild load.

java.lang.NullPointerException: null
 at org.neo4j.ogm.metadata.MetaData.classInfo(MetaData.java:123)
 at org.neo4j.ogm.context.GraphEntityMapper.executePostLoad(GraphEntityMapper.java:193)
 at org.neo4j.ogm.context.GraphEntityMapper.executePostLoad(GraphEntityMapper.java:180)
 at org.neo4j.ogm.context.GraphEntityMapper.map(GraphEntityMapper.java:120)
 at org.neo4j.ogm.context.GraphEntityMapper.map(GraphEntityMapper.java:83)
 at org.neo4j.ogm.context.RestModelMapper.map(RestModelMapper.java:84)
 at org.neo4j.ogm.session.delegates.ExecuteQueriesDelegate.lambda$query$0(ExecuteQueriesDelegate.java:137)
 at org.neo4j.ogm.session.Neo4jSession.doInTransaction(Neo4jSession.java:590)
 at org.neo4j.ogm.session.Neo4jSession.doInTransaction(Neo4jSession.java:564)
 at org.neo4j.ogm.session.delegates.ExecuteQueriesDelegate.query(ExecuteQueriesDelegate.java:134)
 at org.neo4j.ogm.session.Neo4jSession.query(Neo4jSession.java:435)

I have a Micronaut (Java) application that uses Neo4J-OGM, executes the query using Session on a database in Aura (cloud service).

Any idea why this call fail sometimes and work other times? Especially if there are no simultaneous calls.

Could. you provide us more insights on your problem?
How does the domain object looks like, you are trying to get out of the call?
What query do you issue?

The message only tells me that Neo4j-OGM tries to find a class that is not registered in the mapping context.

Yeah,
So I have (Portfolio)-[:HAS_ASSET]->(Asset)-[:HAS_BUILDING]->(Building)-[:HAS_ADDRESS]->(Address)

I am trying to get my building using UUID and populate Asset and Address of the building.

The query looks like this:

MATCH (b:Building) WHERE b.uuid = $buildingUuid WITH b RETURN b, [(b)-[r1:HAS_ADDRESS]-(addr:Address)|[r1, addr]], [(b)<-[r2:HAS_BUILDING]-(a:Asset)|[r2, a, [[(a)<-[r3:HAS_ASSET]-(p:Portfolio) | [r3, p]]]]] with params {buildingUuid=e1168f32-598a-40b4-b7f5-3be8b2a3c557}

It is a simple REST based application that works okay under low load. AS soon as I send multiple requests at the same time, some calls fail with the error above.