discordApiDismissibleContentArbitrate

Seen 5 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/20261030T222341_sourcedandsoldtothehighestbidder, step 1: goto /channels/@me: 401, 308 ms

Sent:

{
  "candidates": [
    {
      "content": 816
    }
  ]
}

Answered:

{
  "message": "401: Unauthorized",
  "code": 0
}

runs/inspect/20261030T222341_sourcedandsoldtothehighestbidder, step 2: snapshot: 200, 495 ms

Sent:

{
  "candidates": [
    {
      "content": 816
    }
  ]
}

Answered:

{
  "candidates": [
    {
      "content": 816,
      "weight": 1
    }
  ]
}

runs/inspect/20261028T062914_sourcedandsoldtothehighestbidder, step 5: click e40: 200, 428 ms

Sent:

{
  "candidates": [
    {
      "content": 816
    }
  ]
}

Answered:

{
  "candidates": [
    {
      "content": 816,
      "weight": 1
    }
  ]
}

What it does

Asks which promo or tip (dismissible content) the client may show now, so only one shows at a time.

What our machine does with it

Nothing in log-cli waits for it or reads it. It is part of what Discord's client loads around the page; a watch or a send never depends on it.

What can go wrong

The account carries on whatever it answers; a failure here changes nothing for our steps.