Activity response generation fails with "not able to access this record" when a table write ACL condition or skill role restriction blocks the access checkIssue Triggering an activity response generation skill from the Additional comments field of a Request, Requested item, or Catalog task record in Service Operations Workspace fails with: Activity response generation failed because it was not able to access this record. Please verify the configured role restrictions for this skill. The user holds the roles documented as required for the skill and can open and read the record normally in the workspace. Symptoms The record-access / role-restriction error returns when activity response generation is triggered.The generation spinner may remain active with no error and no completion.UXCActivityResponseUtil.getTaskGrBySysClassNameWithFallback / _getTaskGrAndValidateUserAccess raises "Failed to find target record for Activity Response Generation."Access checks may log hasAccess= false for the target table.No entry is written to sys_generative_ai_log for the failed attempt.The invoking transaction returns HTTP 200.The user can open and view the same record in the workspace.Granting the expected roles to the user does not resolve the behavior on its own. Release No specific release Cause Activity response generation validates read and write access against the target record before the capability executes. Either configuration below causes that validation to fail while the user still appears to hold the correct roles. Restrictive condition on the table write ACL A write ACL on the target table carrying a condition such as current.isNewRecord() grants write access only while the record is new, so the access check cannot pass against an existing record. Mismatch between the skill ACL and the Role restrictions to skill configuration The capability's Access Control List may require one role, for example ai_agent_users, while the corresponding record in sys_agent_access_role_configuration lists only another, for example itil. When the two do not align, the capability cannot fetch its configuration and complete the access validation. Resolution Identify the table backing the failing skill: sc_request for Request, sc_req_item for Requested item, sc_task for Catalog task.On <instance>, open the write ACL applying to that table and review its condition and script for restrictions that exclude existing records, such as current.isNewRecord().Remove or disable the restrictive condition so the read/write access check can evaluate against existing records.Open the corresponding sys_agent_access_role_configuration record for the skill and compare the roles listed there against the roles required by the skill's Access Control List.Add any required role missing from the Role restrictions to skill configuration so the two align.Clear the instance cache if required by local change procedure.Open an existing record of that table in Service Operations Workspace and trigger activity response generation from Additional comments.Repeat for the remaining affected tables. Do not broadly weaken table ACLs to restore the capability. Confirm the removed condition is not required by another business or security process, validate in a sub-production instance, and test with both authorized and unauthorized users before promoting. Related Links https://www.servicenow.com/docs/r/intelligent-experiences/aia-acl-configuration.html Deny-by-default ACL configuration for AI agentic typeshttps://www.servicenow.com/docs/r/it-service-management/now-assist-for-it-service-management-itsm/summarize-request-related-activity-response-generation.html Generate a response to Request Management records by using Now Assist for ITSM