Skip to content

Commit 2f2381c

Browse files
committed
Generate gql-errors index.adoc file
1 parent ba5cc44 commit 2f2381c

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

modules/ROOT/pages/errors/gql-errors/index.adoc

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,8 @@ Please note that while GQLSTATUS codes remain stable (any changes to them will b
1212
For this reason, parsing the status descriptions or incorporating them into scripts is not recommended.
1313
====
1414

15-
[[connection-exceptions]]
16-
== Connection exceptions
15+
[[connection-exception]]
16+
== Connection exception
1717

1818
Connection exceptions occur when the client (e.g. Browser/Bloom/Cypher Shell) is unable to connect to the server for various reasons such as network issues, server-side routing being disabled, or the database being unavailable, etc.
1919

@@ -29,12 +29,10 @@ Status description:: error: connection exception - transaction resolution unknow
2929

3030
Status description:: error: connection exception - unable to connect to database. Unable to connect to database `{ <<db>> }`. Unable to get bolt address of the leader. Check the status of the database. Retrying your request at a later time may succeed.
3131

32-
3332
=== xref:errors/gql-errors/08N01.adoc[08N01]
3433

3534
Status description:: error: connection exception - unable to write to database. Unable to write to database `{ <<db>> }` on this server. Server-side routing is disabled. Either connect to the database leader directly or enable server-side routing by setting `{ <<cfgSetting>> }=true`.
3635

37-
3836
=== xref:errors/gql-errors/08N02.adoc[08N02]
3937

4038
Status description:: error: connection exception - unable to connect to database. Unable to connect to database `{ <<db>> }`. Server-side routing is disabled. Either connect to `{ $db }` directly, or enable server-side routing by setting `{ <<cfgSetting>> }=true`.

0 commit comments

Comments
 (0)