# QA Uniqueness is enabled but not working

Deprecated

- Published on Oct 29, 2024
- 1 minute(s) read

This article describes an issue in versions of Hyperscience that are not documented on this site.

## Issue

The same keyer completes multiple Supervision and QA tasks for the same document, even when the **QA uniqueness** setting is enabled.

## Affected versions

Versions prior to v33.1.0

## Affected configurations

All configurations

## Cause

The **QA uniqueness timeout** setting allows QA Uniqueness to be ignored when other keyers are unavailable, causing the system to potentially assign tasks to the original keyer.

## Solution / Workaround

Adjust the **QA uniqueness timeout** setting according to your needs. If you need more time to pass before tasks are assigned back to the same user, you can extend the time configured in this setting by following these steps:

1. Go to **Administration** > **Settings**.
2. Click **Edit** next to **Quality Assurance Uniqueness**.
3. In **QA uniqueness timeout**, adjust the amount of time to meet your needs.