Yokohama Patch 7 Hotfix 5

  • Release version: Yokohama
  • Updated November 20, 2025
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Yokohama Patch 7 Hotfix 5

    The Yokohama Patch 7 Hotfix 5 release, updated on November 20, 2025, addresses key issues within the ServiceNow Yokohama platform. This update focuses on resolving problems related to API behavior, Virtual Agent session management, and concurrent workflow execution. It is part of the Yokohama release family and is compatible for upgrade from earlier Yokohama patches and hotfixes.

    Show full answer Show less

    Key Fixes and Improvements

    • setJournalEntry API Correction: Fixed an issue where the setJournalEntry(data, 'user name') API did not set the syscreatedby field correctly. Now, both sysaudit.user and syscreatedby accurately reflect the passed user, improving audit and tracking consistency.
    • Virtual Agent Session Timeout for AI User: Resolved a problem causing session timeouts when the AI user attempted to upload images during agentic workflows. Previously, the AI user would be logged out immediately after session expiration, preventing image uploads. This fix ensures stable session handling and successful image attachment in workflows.
    • Concurrent Agentic Workflow Execution: Addressed an issue where multiple workflows triggered simultaneously would result in only one workflow executing successfully, while others failed with a "No session ID found" error. Now, each workflow execution plan independently manages its session ID, allowing all workflows to proceed concurrently without failure.

    Upgrade Considerations

    This hotfix can be safely applied as an upgrade from any prior Yokohama Patch or Hotfix versions, including Patch 7 Hotfix 4 down to Patch 1, as well as previous security and notable fixes. Customers should ensure they upgrade to the latest patch containing the fixes relevant to their environment to benefit from all resolved issues.

    Additional Information

    • This release supports ServiceNow AI Platform features now also available in Regulated Market environments, supporting isolated environment deployments.
    • For upgrade procedures and the ServiceNow release cycle, customers should refer to official ServiceNow documentation for best practices and scheduling.

    The Yokohama Patch 7 Hotfix 5 release contains fixes to these problems.

    Build information:
    Build date: 11-16-2025_1204
    Build tag: glide-yokohama-12-18-2024__patch7-hotfix5-11-11-2025
    Important:
    For more information about how to upgrade an instance, see ServiceNow upgrades.

    For more information about the release cycle, see the ServiceNow Release Cycle.

    Note:
    This ServiceNow AI Platform major family release is now available in ServiceNow's Regulated Market environments. For more information about services available in isolated environments, see KB0743854.

    Fixed problem

    Problem Short description Description Steps to reproduce

    History Set

    PRB1892171

    KB2565900

    		 setJournalEntry(data, 'user name') API doesn't work as expected When the API setJournalEntry(data, 'user name')​ is used, the sys_audit.user correctly reflects the user passed into the API, but sys_created_by captures the user that's currently logged in.

    Refer to the listed KB article for details.

    Virtual Agent

    PRB1936445

    		 Instance is getting 'session out' because the AI user doesn't work properly During the agentic workflow, the instance calls the image processor agent and asks to upload an image. After some time, the session times out. This only happens for the AI user; it works correctly for the dynamic user.
    1. Log in to an instance.
    2. Navigate to AI Studio.
    3. Select Create Work Order.
    4. Save it.
    5. Try to create a work order with a description.
    6. Say 'yes' to 'create a work order'.
    7. When it asks to upload an image, select the link.
    8. Attach an image from local.

    Expected behavior: It doesn't session out. Ideally, it should attach the image to the work order.

    Actual behavior: The instance says 'session out' and logs out the user. Every time the user attempts to log in again, it immediately logs out.

    Virtual Agent

    PRB1947698

    		 Only one agentic workflow executes successfully when the same trigger fires simultaneously When a workflow trigger fires simultaneously multiple times, only one of the resulting agentic workflows executes successfully. The other workflows terminate immediately with an error indicating that no session ID could be found. Each trigger correctly creates a new execution plan and a new conversation record, but only one conversation proceeds, while the others fail at the start.
    1. Create the agentic workflow named 'Test multiple case executions'.
    2. Select three or more case records and update them simultaneously so that the trigger fires for all at once.
    3. Notice that the three execution plans (sn_aia_execution_plan) and three conversation records are created. Only one conversation and execution plan executes successfully. The other conversations don't continue after the first task with the error 'No session ID found'.

    Expected behavior: Each triggered workflow should independently create or resolve its own valid session so that all conversations execute successfully, even under concurrent trigger conditions.

    Actual behavior: Only one conversation executes successfully. The other conversations either terminate immediately or don't continue after the first task with 'No session ID found' error.

    Fixes included

    Unless any exceptions are noted, you can safely upgrade to this release version from any of the versions listed below. These prior versions contain PRB fixes that are also included with this release. Be sure to upgrade to the latest listed patch that includes all of the PRB fixes you are interested in.