Partial success responses in GraphQL - Step-by-Step Execution

Concept Flow - Partial success responses

Client sends GraphQL query

↓

Server processes query

↓

Check for errors in parts of query

↓

Return data

↓

Include errors field

↓

Client receives partial data + errors

↓

Client handles partial success

The server processes a GraphQL query and returns data for successful parts plus errors for failed parts, enabling partial success responses.

Execution Sample

GraphQL

query {
  user(id: "1") {
    name
    posts {
      title
    }
  }
}

Client requests user name and posts; server returns available data plus errors if some parts fail.

Execution Table

Step	Action	Evaluation	Result
1	Receive query for user with id '1'	Query parsed	Valid query structure
2	Fetch user data	User exists	User data found: name = 'Alice'
3	Fetch posts for user	Posts fetch error	Posts data unavailable due to error
4	Prepare response	Partial success	Data includes user name; posts field null
5	Add errors field	Include error details	Errors array includes posts fetch error
6	Send response to client	Response sent	Client receives partial data + errors

💡 Response sent with partial data and errors because posts fetch failed

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
userData	null	{"name": "Alice"}	{"name": "Alice"}	{"name": "Alice"}	{"name": "Alice"}
postsData	null	null	error	null	null
responseData	null	null	null	{"user": {"name": "Alice", "posts": null}}	{"user": {"name": "Alice", "posts": null}, "errors": [{"message": "Posts fetch failed"}]}

Key Moments - 2 Insights

Why does the response include data even though there is an error?

Because GraphQL supports partial success, the server returns data for parts that succeeded (user name) and includes errors for parts that failed (posts). See execution_table step 4 and 5.

What does the 'errors' field in the response represent?

It contains details about which parts of the query failed and why, allowing the client to understand partial failures. See execution_table step 5.

Visual Quiz - 3 Questions

Look at the execution_table at step 3, what happened when fetching posts?

A Posts data was successfully fetched

B Posts data fetch caused an error

C Posts data was not requested

D Posts data was empty but no error

💡 Hint

Check the 'Evaluation' and 'Result' columns at step 3 in execution_table

At which step does the server add the errors field to the response?

A Step 2

B Step 3

C Step 5

D Step 6

💡 Hint

Look for the step mentioning 'Add errors field' in execution_table

If the posts data fetch succeeded, how would the responseData variable change after step 4?

A posts field would contain posts data

B responseData would be null

C posts field would be null

D errors field would still be present

💡 Hint

See variable_tracker postsData and responseData values after step 4

Concept Snapshot

Partial success responses in GraphQL:
- Server returns data for successful parts
- Errors field contains details of failures
- Client receives partial data + errors
- Enables graceful handling of partial failures
- Query continues despite some errors

Full Transcript

In GraphQL partial success responses, the server processes the query and returns data for parts that succeed. If some parts fail, the server includes an errors field describing those failures. This allows the client to receive useful data even when some parts of the query cannot be fulfilled. For example, if fetching user posts fails but user name is found, the response includes the user name and an error about posts. This approach helps clients handle partial data gracefully.

Practice

1. What does a partial success response in GraphQL typically include?

easy

A. Only the data field with no errors

B. Both data and errors fields

C. Only the errors field with no data

D. Neither data nor errors fields

Solution

1. Step 1: Understand partial success response structure

   Partial success responses include both data that was successfully fetched and errors for parts that failed.

2. Step 2: Identify fields present in response

   The response contains a data field with available data and an errors field describing issues.

3. Final Answer:

   Both data and errors fields -> Option B

4. Quick Check:

   Partial success = data + errors [OK]

Hint: Partial success means data and errors appear together [OK]

Common Mistakes:

• Thinking partial success returns only data
• Assuming errors field is empty on partial success
• Believing partial success means no errors

2. Which of the following is the correct way to check for errors in a GraphQL partial success response?

easy

A. Check if response.errors exists and is not empty

B. Check if response.data is null

C. Check if response.status equals 200

D. Check if response.message contains 'error'

Solution

1. Step 1: Understand error reporting in GraphQL

   Errors are reported in the errors field as an array when present.

2. Step 2: Identify correct error check

   Checking if response.errors exists and is not empty correctly detects errors.

3. Final Answer:

   Check if response.errors exists and is not empty -> Option A

4. Quick Check:

   Errors field presence = error check [OK]

Hint: Look for non-empty errors array to detect issues [OK]

Common Mistakes:

• Checking data for null instead of errors
• Using HTTP status code instead of errors field
• Looking for message text instead of errors array

3. Given this GraphQL response:

{"data": {"user": null}, "errors": [{"message": "User not found"}]}

What should the client do?

medium

A. Check the errors and handle missing user

B. Ignore the errors field and proceed

C. Retry the query immediately without changes

D. Use the user data as valid

Solution

1. Step 1: Analyze the response data and errors

   The user field is null and there is an error message "User not found".

2. Step 2: Decide client action based on partial success

   The client should check errors and handle the missing user data appropriately, not ignore errors or blindly use null data.

3. Final Answer:

   Check the errors and handle missing user -> Option A

4. Quick Check:

   Errors present + null data = handle carefully [OK]

Hint: Null data with errors means handle missing info [OK]

Common Mistakes:

• Using null data as valid without checking errors
• Ignoring errors field completely
• Retrying query without fixing cause

4. You receive this partial success response:

{"data": {"posts": [{"id": "1", "title": "Hello"}]}, "errors": [{"message": "Failed to fetch comments"}]}

What is the likely cause of the error?

medium

A. Network connection lost before response

B. The entire query failed and returned no data

C. Syntax error in the GraphQL query

D. Posts data fetched but comments part failed

Solution

1. Step 1: Examine data and errors in response

   Data for posts is present, but error message says "Failed to fetch comments".

2. Step 2: Interpret partial success meaning

   Partial success means some parts succeeded (posts), others failed (comments).

3. Final Answer:

   Posts data fetched but comments part failed -> Option D

4. Quick Check:

   Data present + error message = partial failure [OK]

Hint: Data present means partial success, check error message for failed parts [OK]

Common Mistakes:

• Assuming entire query failed with some data
• Thinking syntax error causes partial success
• Blaming network loss without evidence

5. How can you design a GraphQL query to handle partial success gracefully when fetching users and their posts, knowing posts might fail?

hard

A. Ignore errors and always use posts data blindly

B. Split into two separate queries to avoid partial success

C. Request users and posts in one query and check errors for posts failures

D. Use a mutation instead of a query to avoid partial success

Solution

1. Step 1: Understand partial success handling in GraphQL

   GraphQL allows querying multiple fields; some may succeed while others fail, returning partial success.

2. Step 2: Design query and client logic

   Request both users and posts in one query, then check errors to handle posts failures gracefully without losing users data.

3. Final Answer:

   Request users and posts in one query and check errors for posts failures -> Option C

4. Quick Check:

   One query + error check = graceful partial success [OK]

Hint: Query all, then check errors to handle partial failures [OK]

Common Mistakes:

• Splitting queries unnecessarily
• Ignoring errors and using incomplete data
• Confusing mutations with queries