Skip to main content

​
Gamebook Actions Not Available

Cause: Gamebook service principals were not authorized during onboarding. Fix:
  1. Go to Settings → Workspace Settings → Module Configuration
  2. Look for the Gamebook Authorization step
  3. Click to re-authorize the Gamebook service principals
  4. Use Global Admin credentials for the consent flow

​
Action Failed — Generic Error

Cause: The target entity may no longer exist, the integration may have lost connectivity, or the action isn’t supported for the entity state. Fix:
  1. Verify the target entity still exists in the source system (e.g., the device is still in Defender, the user is still in Entra ID)
  2. Check that the workspace module is still configured (Settings → Module Configuration)
  3. Retry the action
  4. If it fails again, contact support@contraforce.com with the incident ID, action attempted, and error message

​
”Isolate Device” Failed

Cause: The device may already be isolated, offline, or not onboarded to Defender for Endpoint. Fix:
  1. Check the device status in the Endpoints page
  2. Verify the device is onboarded to Defender for Endpoint (Plan 1, Plan 2, or Defender for Business)
  3. If the device is already isolated, use Unisolate first if you need to re-isolate

​
”Disable Account” Failed

Cause: The user account may already be disabled, or ContraForce may not have sufficient permissions. Fix:
  1. Check the account status in Entra ID
  2. Verify the ContraForce Gamebooks for Identity service principal is authorized
  3. Re-run consent if needed

​
Action Stuck on “Pending”

Cause: The action may require approval or may be waiting for the backend to process. Fix:
  1. Check if the action requires approval — look for “Pending Approval” status
  2. If approval is required, the designated approver needs to review
  3. If it’s stuck for more than 15 minutes without an approval requirement, contact support