Fortunately it came back in a few minutes. I did it twice. Here is the query: PROFILE MATCH (start:portfolio {IRI:'ea3376e7-ad79-4e2a-9620-eff1e5e1fcb5'}), (end:portfolio {IRI:'9568f210-f5d5-4e8e-9966-444fa173fb83'}) CALL apoc.path.expandConfig(start, { terminatorNodes: [end], bfs: true, uniqueness: 'NODE_PATH', maxLevel: 5 }) YIELD path RETURN count(path); This was in an effort to explore with ChatGPT some optimization options for the following query. I don't think ChatGPT knows much about Cypher. PROFILE MATCH (start:portfolio {IRI:'ea3376e7-ad79-4e2a-9620-eff1e5e1fcb5'}), (end:portfolio {IRI:'9568f210-f5d5-4e8e-9966-444fa173fb83'}) MATCH p = (start)-[*..5]-(end) WHERE ALL(n IN nodes(p)[1..-1] WHERE NONE(lbl IN labels(n) WHERE lbl IN ['person','portfolio','metric','root'])) AND ALL(sx IN nodes(p) WHERE SINGLE(sy IN nodes(p) WHERE sy = sx)) WITH p WITH [n IN nodes(p) | apoc.map .removeKeys(properties(n), ['description','isDefinedBy','seeAlso','vectorUpdated','_updated','_created','identity'])] AS pn, [r IN relationships(p) | { IRI: r.IRI, start: startNode(r).IRI, end: endNode(r).IRI, type: type(r), level: r.level }] AS pr RETURN pn, pr, 'ea3376e7-ad79-4e2a-9620-eff1e5e1fcb5' AS from_portfolio, '9568f210-f5d5-4e8e-9966-444fa173fb83' AS to_portfolio, 'psp' AS semantic;