Mission 01 Mission 01 Error Resolution Practice Guide
📥 Practice Input
- •
day6_meeting_notes.md(meeting minutes)
💾 Practice output (Output)
- •
day6_error_report.md
1. Story and practice background
After creating a dashboard screen prototype and implementing the API data fetch function to test virtual server integration, a series of unexpected errors occurred. We receive Codex's diagnostic prescription for the error in question, trace the error cause, and ultimately prove that the result runs stably.
2. Learning objectives
- Identify HTTP Status 404 and CORS errors that occur when calling a virtual server.
- Understand the fundamental parsing cause of SyntaxError that occurs when the JSON format of the response is broken.
- Create an error report summarizing the debugging results, action details, and measures to prevent future recurrence.
🛠️Practical guide to follow along
- Create file for practice: Click the download button below
day6_meeting_notes.mdfileautomation/Save it within the folder. - CORS/JSON parsing diagnostics: I hand over the collected error sentences and my original code to the Codex Client to help explain the structural causality of the problem.
- Permanent error report: Fill out and check the error report form (`day6_error_report.md`) based on the correction code guidelines diagnosed and suggested by AI.
Download practice materials
Codex request prompt
Mission 01 Prompt 'SyntaxError: Unexpected token' occurred when calling the server.
4. Example results
Codex analyzes the meeting transcript and outputs normalized data entity mappings and a Mermaid ERD script as shown below.
| file name | Error type | Diagnosis Cause | corrective action |
|---|---|---|---|
| day6_error_report.md | SyntaxError: Unexpected token < in JSON | HTML 404 response returned due to typo in server call URL address | URL correction and content-type verification |
5. AI utilization points
- CORS/parsing cause analysis: Compare and analyze domain differences between the server and client or differences in the type of HTTP response content.
- Derivation of Prevention Matrix: We build a standard processing utility guide to prevent the same phenomenon from recurring when calling other APIs in the future.