@@ -215,7 +215,17 @@ cv api Job.Torcrm_Resque_Process -vvv
```
Once the problem is fixed, the kill switch can be reset by going to
"CiviCRM > Administer > Tor CRM Settings" in the web interface.
"CiviCRM > Administer > Tor CRM Settings" in the web interface. Note
that there's somewhat of a double-negative in the kill switch
configuration. The form is:
Resque Off Switch [0]
Set to 0 to disable the off/kill switch. This gets set to 1 by the "Resque" Scheduled Job when an error is detected. When that happens, check the CiviCRM "ConfigAndLog" logs, or under Administer > Console > View Log
The "Resque Off Switch" is the kill switch. When it's set to zero
("0", as above), it's disabled, which means normal operation and the
queue is processed. It's set to "1" when an error is raised, and
should be set back to "0" when the issue is fixed.
See [tpo/web/civicrm#144](https://gitlab.torproject.org/tpo/web/civicrm/-/issues/144) for an example of such a kill switch
