Storing post-function with expired WebSudo causing change in Run As

Description

Example:
I am editing a scripted post function. If its not a huge development I am doing those directly in workflow.
Mostly, my scripted functions are run as some robot user.
Time to time, the time I am editing the code goes above the WebSudo limit.
And now here comes the tricky part.
When I hit update post function:
Current behavior:
1) I received WebSudo window
2) I received "We are unsure, retry window"
3) The post function is stored, BUT the Run as is always current user.
Expected behavior:
The post function is stored with run as I choose

Its not something critical, its just bothering to always re-edit post function, change again run-as as store within WebSudo.

Environment

Environment independent. Or at least happening on all of my clients.

Customer Info

None

Assignee

David Fischer [Innovalog]

Reporter

Tomáš Vrabec

Labels

None

Internal Complexity

Unknown

Internal Value

Unknown

SEN

None

Requires documentation

None

Impact

Level 4

Priority

Major
Configure