checkbox "Temporarily disabled" needs direct database access

REST API throw same error. Any suggestions ?

{
  "responseStatus": {
    "message": "The process task needs direct database access but the server cannot access the database directly."
  },
  "errorString": "The process task needs direct database access but the server cannot access the database directly.",
  "exceptions": [
    {
      "number": 810336,
      "message": "The process task needs direct database access but the server cannot access the database directly."
    }
  ]
}

One process, that will be triggered by setting the mentioned flag, contains a pure SQL Job Task that cannot be run by a Job Service without a direct SQL connection.

strange behavior to be honest.
even if i change "Temporarily disabled" flag with parameters: Job description, Description, Company member the result is the same - error "The process task needs direct database access but the server cannot access the database directly"

You may want to look at the processes assigned to the ADSAccount table. If you change the "Temporarily disabled" flag, this update flows to the linked accounts.

Do you have only one Job Service or do you have more than one (one for SQL Tasks and one for the AD jobs)?

I have multiple servers (shorten the names for simplicity):

with direct connection to DB - JS1 (one im connector, sql processing server, update server, csv connector)

via AppServer - JS2, JS3 (almost identical: active directory connector, one im connector, csv connector)

Do you have any custom processes at the person table or at the ADSAccount table? If so, please check the assigned servers for the task. At least one task executing the SQLComponent or the DelayComponent is configured to run on JS2 or JS3 instead of JS1.

I haven't any custom processes.

What version are you using?

8.1.4.179

Okay. To identify which process generation is troublesome, you may either turn on the process generation log as described here https://support.oneidentity.com/identity-manager/kb/261074/how-to-enable-trace-logging and https://support.oneidentity.com/technical-documents/identity-manager/8.1/process-monitoring-and-troubleshooting-guide/9#TOPIC-1133939 or you try to use the debugging feature of the Object Browser which is shown here https://support.oneidentity.com/technical-documents/identity-manager/8.1.4/configuration-guide/77#TOPIC-1529924