Rejected tasks

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

Example for a JSON block

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

You can ban a performer from your project for a given number of days, hours, minutes (at a time or in total) or permanently.

Ban for 10 days
{
   "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": {
                  "type": "RESTRICTION_V2",
                  "parameters": {
                     "scope": "PROJECT",
                     "duration_unit": "DAYS",
                     "duration": 10,
                     "private_comment": "Requester rejected 40% of assignments"
                  }
               }
            }
         ]
      }
   ]
}

To set a different ban period, change the applicable parameter for the action key:

{
   ...
               "action": {
                  "type": "RESTRICTION_V2",
                  "parameters": {
                     "scope": "PROJECT",
                     "duration_unit": "HOURS",
                     "duration": 12,
                     "private_comment": "Requester rejected 40% of assignments"
                  }
               }
   ...
}

Keys

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 with non-automatic acceptance.

  • rejected_assignments_rate — The percentage of pool tasks performed by the user that were rejected during non-automatic 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

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 with non-automatic acceptance.

  • rejected_assignments_rate — The percentage of pool tasks performed by the user that were rejected during non-automatic 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