{"version":"2.1.268","anchor":"ui-closerender-engine-adds-cross-instance-requestid-guard","canonical_anchor":"ui-closerender-engine-adds-cross-instance-requestid-guard","heading":"UI-close\/render engine adds cross-instance requestId guard","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/ui-closerender-engine-adds-cross-instance-requestid-guard","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### UI-close\/render engine adds cross-instance requestId guard\n\nUI rendering now rejects events with a requestId from a different session instance\n\n**What**\n\nThe validator that checks arguments for `ui.render` events (used to draw interactive UI elements) now also rejects an event if its `requestId` doesn't match the specific instance the UI element was originally drawn in, returning an error about \"a requestId other than the instance the element was drawn in\". Separately, the logging for `ui.close` events now logs the event's `kind` rather than the raw event object.\n\n**Why**\n\nThis prevents a UI event meant for one session or instance from being mistakenly applied to a different one, closing a potential cross-instance mix-up when multiple UI elements or sessions are active.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}