Generated cypher with ARROWS.APP returns a strange error

This query has been generated by arrows.app, and returns the following strange errors.
I examinated the query, but didn't find any visible error.

MERGE (n28:Cart {uuid: "32c7b209-5a8d-4a92-98d7-35c30c9a4117", createdAt: "2025-02-01T15:00:00Z+1", valueOfGoods: 128.10, vat: 26.90, otherTaxes: NULL, totalToPay: 155.00})-[:REMOVED {at: NULL}]->(n140:Price {listPrice: 310.00, currency: "EUR", discount: "50%", discountedPrice: 155.00, uuid: "1f41876f-a71b-47ba-a0d8-0f452f3b0ea8"})<-[:ADDED {at: "2025-02-01:16:00:00T+1"}]-(n28)<-[:HAS_CART {status: "pending", residualAmount: 15.00}]-(n25:User {uuid: "6214648b-407e-47a1-96f9-ef85b7035e01", nickname: "PDP"})-[:HAS_CONVERSATION {Start: "2025-02-01", End: NULL}]->(n26:Conversation)-[:ADD_REMOVE_ITEM]->(n28)-[:HAS_AMOUNT_PAYABLE]->(n131:amountPayable {amountOwed: 155.00, amountPayed: 140.00, residualAmount: 15.00})-[:PAYMENT]->(:Payment:Amex {amount: 35.00, currency: "EUR", date: "2025-02-01T16:30:00Z+1"})

MERGE (n135:Nick:Singleton {uuid: apoc.create.uuid()})-[:ANSWERS_QUESTION {att: NULL}]->(n134:Step {initiate: "Come posso aiutarti oggi con il modello Sneakers Ash Race??", question: "Vorrei sapere se รจ disponibile in Rosso scuro", answer: "esiste questo colore, ma soltanto nel numero 37 e 41"})<-[:ASKS_QUESTION {att: NULL}]-(n25)-[:BELONGS_TO]->(:Customer {uuid: "b1cdbe2e-63bb-4eb0-94f8-cecc581f3916", shortName: "Lonigro"})<-[:SERVES]-(n135)

MERGE (n26)-[:IS_COMPOSED_OF {at: "2025-02-01T15:45:00Z+1"}]->(n134)<-[:INITIATES {att: NULL}]-(n135)

MERGE (:Payment:Visa {amount: 35.00, currency: "EUR", date: "2025-02-01T16:31:00Z+1"})<-[:PAYMENT]-(n131)-[:PAYMENT]->(:Payment:Mastercard {amount: 35.00, currency: "EUR", date: "2025-02-01T16:32:00Z+1"})

MERGE (n131)-[:PAYMENT]->(:Payment:Paypal {amount: 35.00, currency: "EUR", date: "2025-02-01T16:33:00Z+1"})

MERGE (n140)-[:REVIEWED_BY {at: "2025-02-10T23:00T+1", star: 4, description: "A fantastic pair of shoes"}]->(n25)

This query has been generated by arrows.app, and returns the following strange errors.

Found no access plan for a pattern relationship in a connected component. This must not happen.

@paolodipietro58

any details of what Neo4j version is in play here?
This Found no access plan for a pattern ..... ...... error was once reported against Neo4j 3.5 and it was fixed but I suspect / hope you are not running such an old release

also is the cypher being played back against a empty database or one already populated

@dana_canzano

Sorry, I completely missed the environment description, and no, I'm using the latest version available (with the limit of the global coexistence of the tools:

Neo4j enterprise v5.26.2. (not 5.26.4 because the GDSL is only available until the 5.26.2)
GDSL v2.1.3.2
APOC 5.26.4

The cypher was played against a database already populated with compatible data.

But, as you suggest me, I now have run against an empty DB and the resulti was quite different:
Cannot merge the following node because of null property value for 'otherTaxes': (:Cart {otherTaxes: null})

As this should be a MetaModel, I want to have into the model all the expected attributes, not having all together an explicit value, like otherTaxes, which can generally be present, but in this case it is not and have a null value (try to explain better: I don't expect that the property will have a 0 value, but that it would be missed at all, but one could expect to find it).

Off course, being Neo4j skemaless, these are only the basic attributes used, but nobody prevents us from adding new attributes should the need arise.

So, I redefined the Query, removing all the attributes will NULL value present in the MERGE body, and add those at the end as a series of SET statements.

This solved the problem in a query against the empty database. The same query running in a semi populated database failed with

Neo.DatabaseError.Statement.ExecutionFailed Found no access plan for a pattern relationship in a connected component. This must not happen.

TY