ajaxBz

Seen 20 time(s) in 2 run(s).

What it sent and what came back (the newest 3 from our runs)

Read from each run's own recording (rule 73), secrets and signed link tokens taken out. Kept in ~/.logCli/rea/clientFacts.json, so it stays after the run is pruned.

runs/inspect/20261103T185330_mattinferencesaver, upload: paulie.jpg handed to the file chooser: 200, 178 ms

Sent:

{
  "query": {
    "__d": "www",
    "ph": "C3",
    "qpl_active_flow_ids": "521485957"
  },
  "body": null
}

Answered:

{
  "__ar": 1,
  "rid": "AhzVH6gBp03M67VQRDHXuY3",
  "payload": null,
  "lid": "7704020494487878755"
}

runs/inspect/20261103T185330_mattinferencesaver, step 4: click e783: 200, 182 ms

Sent:

{
  "query": {
    "__d": "www",
    "ph": "C3"
  },
  "body": null
}

Answered:

{
  "__ar": 1,
  "rid": "AVHNigzxBexyRQJVtnEiHoC",
  "payload": null,
  "lid": "7704020622278303489"
}

runs/inspect/20261103T180010_mattinferencesaver, step 1: goto /: 200, 202 ms

Sent:

{
  "query": {
    "__d": "www",
    "ph": "C3"
  },
  "body": {
    "------WebKitFormBoundaryhx5lADbY1fBdIwIw\r\nContent-Disposition: form-data; name": "\"ts\"\r\n\r\n1793728825702\r\n------WebKitFormBoundaryhx5lADbY1fBdIwIw\r\nContent-Disposition: form-data; name=\"q\"\r\n\r\n[{\"app_id\":\"936619743392459\",\"posts\":[[\"falco:ig_web_page_view\",{\"e\":\"{\\\"module\\\":\\\"CAAIGLoginHomepage\\\",\\\"nav_chain\\\":\\\"CAAIGLoginHomepageRoot:CAAIGLoginHomepage:1:via_cold_start\\\",\\\"referrer\\\":\\\"\\\",\\\"url\\\":\\\"https://www.instagram.com/\\\",\\\"web_analytics_session_id\\\":\\\"c78ouj:c3tx3c:zgmoiu\\… (699 chars)"
  }
}

Answered:

{
  "__ar": 1,
  "rid": "A-c31ZV38ap15654PxyR7Uz",
  "payload": null,
  "lid": "7704006642877187368"
}

What it does

The web client's own telemetry beacon: it posts a small form (__d: www, ph: C3, a qpl_active_flow_ids value) and Instagram acknowledges with payload: null. It fired 20 times in 2 runs on nearly every step (goto /, snapshot, saveState, clicks, wait 40s, and both file-chooser uploads), each taking 178-273 ms with status 200.

What our machine does with it

Nothing: no log-cli machine waits on it, reads it or sends it. python/instagramApi/engine.py does not use it, because the engine works through instagrapi's private API with no browser, and this beacon only exists inside the web page's own scripts (script3.js, script4.js, script30.js).

What can go wrong

Every recorded call answered 200 with payload: null and no errors. A failure would only mean the page's own telemetry did not land; nothing in our runs decides on it, so it would not change a step.