syncInstagram

Seen 4 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, step 1: goto /direct/t/<id>/: 200, 194 ms

Sent:

{
  "encrypted_data": "AVkCx23qHrA1wtXXaH7_92KvmYRWKSPiiiCQ44O9nkA3lJkd6AhyxeLjerv2y-d9SfUN",
  "__d": "www"
}

Answered:

{
  "__ar": 1,
  "rid": "AZZp8jZxh0mBF7xWvkU9iR_",
  "payload": null,
  "lid": "7704020382008127603"
}

runs/inspect/20261103T180010_mattinferencesaver, step 2: snapshot: 200, 194 ms

Sent:

{
  "encrypted_data": "AVkMDZ5HhMyS7NECMZSpywr6l7_D-u_j6kVRtA-9iZAztFYbGN7j4dIN1s6SfSCH_HX3",
  "__d": "www"
}

Answered:

{
  "__ar": 1,
  "rid": "AcScNTtzGNxYQLjFnYFI5if",
  "payload": null,
  "lid": "7704006797227472939"
}

runs/inspect/20261103T180010_mattinferencesaver, step 3: goto /direct/inbox/: 200, 191 ms

Sent:

{
  "encrypted_data": "AVnHxekJtz7485MUqrWiBM8OIIDKcnaLleI0T8ptBIjKMsxtGDr3RfBAfH06F0mYztv9",
  "__d": "www"
}

Answered:

{
  "__ar": 1,
  "rid": "A53xPGN4JZq8dDBDTr03yRD",
  "payload": null,
  "lid": "7704006912815245066"
}

What it does

A background sync the web client posts with an encrypted_data blob and __d: www, answered payload: null. It fired 4 times in 2 runs on snapshot, goto /direct/inbox/ and goto /direct/t/<id>/ steps, each 191-199 ms with status 200.

What our machine does with it

Nothing: no machine waits on it, reads it or sends it; the blob is opaque to us and the engine's realtime watch does not use /sync/instagram.

What can go wrong

All 4 calls answered 200 with payload: null and no errors. A failure would only mean the page's background sync did not complete, which no run of ours decides on.