View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0025652Return of ReckoningGeneralpublic2026-08-05 17:482026-08-05 17:48
ReporterWholdar Assigned To 
PrioritynormalSeverityminorReproducibilitysometimes
Status newResolutionopen 
Summary0025652: RoR GraphQL API: completed Bastion Stair boss runs can return encounters: []
DescriptionHi!

I found this while pulling Bastion Stair stats from the GraphQL API. Some boss InstanceRuns have completed: true and six scoreboard entries but return encounters: [].

One example:

InstanceRun 3f5d0e0f-9ec3-4f27-9d2a-cf4647371b95
  instance: 163, Thar'Ignan
  completed: true
  scoreboardEntries: 6
  encounters: []

A run with encounter data for the same boss looks like this:

InstanceRun e5d4f0ea-22e7-4939-977a-379c04bcbebb
  instance: 163, Thar'Ignan
  completed: true
  encounters:
    EncounterRun 674207
      encounter: 25
      completed: true
      scoreboardEntries: 6

In the first example there is no EncounterRun object. The list itself is empty.

Is this expected? If it is, what does InstanceRun.completed mean here, and what should I use to confirm that the boss died?
Steps To Reproduce1. POST this query to https://production-api.waremu.com/graphql

query BossRuns($filter: InstanceRunFilterInput) {
  instanceRuns(first: 50, where: $filter, order: { end: DESC }) {
    edges {
      node {
        id start end completed
        instance { id name }
        scoreboardEntries { character { id } }
        encounters {
          id start end completed
          encounter { id name }
          scoreboardEntries { character { id } }
        }
      }
    }
  }
}

2. Use these variables:

{"filter":{"end":{"gte":"2026-08-04T00:00:00.000Z","lt":"2026-08-05T00:00:00.000Z"},"instanceId":{"eq":163}}}

3. Find InstanceRun 3f5d0e0f-9ec3-4f27-9d2a-cf4647371b95 under data.instanceRuns.edges[].node.

4. Its completed value is true, it has six scoreboardEntries, and its encounters value is [].
Additional InformationI re-fetched all examples below from the live API on 2026-08-05.

More completed runs with six scoreboardEntries and encounters: []:

- 2026-08-04 - instance 164 Lord Slaurith - eb4f03ec-d93c-4da0-8993-f09b5263336a
- 2026-08-04 - instance 166 Skull Lord Var'Ithrok - 623e2522-bdef-4a95-85e0-62b8700a8c42
- 2026-07-26 - instance 165 Kaarn the Vanquisher - ed89e340-8ab8-4b67-aebe-6290a616f523
- 2026-07-12 - instance 166 Skull Lord Var'Ithrok - 55c20ced-46eb-4d8b-addd-880ae7325750

More completed runs that include a completed boss EncounterRun with six scoreboard entries:

- 2026-08-03 - instance 166 - c17cdbbe-88cc-4b73-a7a0-cac6f11b49ac - encounter 23 / EncounterRun 674279
- 2026-08-02 - instance 164 - c4959169-450e-44be-bbe7-1e3f429b0504 - encounter 24 / EncounterRun 672964
- 2026-07-26 - instance 165 - eb789ff0-2abe-4872-a284-759b268676c5 - encounter 22 / EncounterRun 665404
- 2026-07-12 - instance 163 - 9714cbd8-5686-4ab1-b564-e1bd29a4660e - encounter 25 / EncounterRun 652296

What I'm assuming:

- Instances 163, 164, 165 and 166 are the separate boss runs. Their names and runs with encounter data pair them with encounters 25, 24, 22 and 23.
- The API gives no parent Bastion Stair run ID. I match them to instance 160 runs using players and times, but that matching isn't needed to see the empty encounters list.
- For now, completed on the outer boss run counts as inferred kill evidence.
TagsNo tags attached.

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2026-08-05 17:48 Wholdar New Issue