Error message: Cannot set the Run-As field to an admin user as a non-admin user

[David Garcia]

Hello,

My co-workers are getting the following error when Fulfilling Requested Items: "Cannot set the Run-As field to an admin user as a non-admin user". I am not sure how to correct this issue. 

This is the business rule that is causing the error message:

Here is the Run as information:

And here are the Access Controls for the Create and Write operations:

Any information would be greatly appreciated.

Thank you.

[James Chun]

Hi @David Garcia,

The OOB Business Role is preventing non-admins (I am guessing your co-workers are non-admin) from populating the run_as field as an admin user. This makes sense because if non-admins can run the script as an admin user, they can have privileged access and cause some issues in the system (e.g. accessing data they shouldn't).

I would recommend just leaving it as it is, why do they need to change the run_as field?

Cheers

[David Garcia]

Hi @James Chun,

I am not sure. This error message started happening about a month ago. I assume it was during an automatic update or something.

If I leave it as-is, is there a way to stop that message from popping up?

[James Chun]

Hi @David Garcia,

What did you mean by 'Fulfilling Requested Items'?

Are the co-workers modifying the Scheduled Job record or something during the process?

[Kieran Anson]

If standard fulfiller users are receiving this message when updating ritms / sctasks, it means something is happening in the same transaction as their update. A good way to look into these issues is to use script tracer, and perform the same action(s) as the fulfiller user. You can then see/rule out scripts being an issue

Script Tracer and debugging scripts (servicenow.com)

As request items have workflows  / flows, it's worth checking if there are any scripts within these that might be performing an update to a scheduled job record