Skip to content

Conversation

@Tanium-Nicole
Copy link
Collaborator

What

Corrected the use of the wrong variable in the Quarantine & Unquarantine playbook when there are enough results from the Tanium API that pagination is required and we need to use the endCursor to get the next page of results.

Why

The use of the wrong variable caused the API call to be incorrect and return a 400 response indicating our graphQL body was not formatted properly.

How do I know this works?

I tested this myself both after manually fixing it in a playbook, and also by redeploying this updated template to confirm it works as expected.

How could I test this myself?

By doing the following:

  1. Deploy the Quarantine & Unquarantine playbook to an Azure environment from this branch
  2. Create a Sentinel Incident with 10 or more hosts that also exist in your Tanium environment
  3. Run each playbook against your incident
  4. Confirm that group "Loop Paginated Response if has multiple pages" executed successfully

@Tanium-Nicole Tanium-Nicole force-pushed the tanium/fix/quarantine-paging branch 2 times, most recently from 30e92bd to 7b0a8be Compare October 2, 2025 17:35
@Tanium-Nicole Tanium-Nicole force-pushed the tanium/fix/quarantine-paging branch from 7b0a8be to b258631 Compare October 2, 2025 17:40
@Tanium-Nicole Tanium-Nicole force-pushed the tanium/fix/quarantine-paging branch from b258631 to 4ca795f Compare October 2, 2025 17:43
@Tanium-Nicole Tanium-Nicole changed the title Tanium/fix/quarantine paging disregard Oct 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants