Has anyone encountered the following: The script deployement has a limited audience (Role A, specific subsidiary). Execute as role is also set to Role A. The script disregards these limitations fully and gets triggered by a user of a different subsidiery and role.