Rejected tasks

You can block access to tasks for users whose responses were rejected by the requester during offline acceptance. To do this, set key values in the quality_control.configs array in the pool settings.

In the example, access to tasks is blocked if 40% of the tasks completed by the user were rejected by the requester. This condition is checked for the first time after 10 tasks have been completed.

{
  "configs": [
    {
      "collector_config": {
        "type": "ACCEPTANCE_RATE",
        "parameters": {
          "history_size": 10
        }
      },
      "rules": [
        {
          "conditions": [
            {
              "key": "total_assignments_count",
              "operator": "GTE",
              "value": 10
            },
            {
              "key": "rejected_assignments_rate",
              "operator": "GT",
              "value": 0.4
            {
          ],
          "action": {
            "parameters": {
              "duration_days": 1,
              "scope": "PROJECT"
            },
            "type": "RESTRICTION"
          }
        }
      ]
    }
  ]
}

Key

Value

Data type

Required during creation

rules.conditions.key
Parameters that are checked in the condition:
  • total_assignments_count — The number of tasks in the pool that the user completed.

  • accepted_assignments_rate — The percentage of pool tasks performed by the user and accepted during offline acceptance.

  • rejected_assignments_rate — The percentage of pool tasks performed by the user that were rejected during offline acceptance.

String

Yes

collector_config.parameters.history_size

The maximum number of recent tasks that the user completed in the project to use for the calculation.

If this field is omitted, the calculation is based on all the tasks that the user completed in the pool.

String

No