From 9b4ab8cd85008fcc7b0691f297b093f3c5375d80 Mon Sep 17 00:00:00 2001 From: enisn Date: Tue, 10 Feb 2026 11:42:53 +0300 Subject: [PATCH 1/3] Clarify Blazor Server entity history limitation in audit logging docs --- docs/en/framework/infrastructure/audit-logging.md | 11 +++++++++++ docs/en/modules/audit-logging-pro.md | 2 ++ 2 files changed, 13 insertions(+) diff --git a/docs/en/framework/infrastructure/audit-logging.md b/docs/en/framework/infrastructure/audit-logging.md index 9811e542ab..b6f2ebf25d 100644 --- a/docs/en/framework/infrastructure/audit-logging.md +++ b/docs/en/framework/infrastructure/audit-logging.md @@ -169,6 +169,17 @@ public class HomeController : AbpController [Application service](../architecture/domain-driven-design/application-services.md) method calls also included into the audit log by default. You can use the `[DisableAuditing]` in service or method level. +> ### Blazor Server Limitation (Entity History) +> +> In `Blazor Server` applications, entity change history is currently not guaranteed to be complete for every UI interaction. +> +> Blazor Server uses SignalR-based event handling, and under some flows the audit scope/action tracking may not align with `DbContext.SaveChanges`, which can cause missing or partial entity change records. +> +> This is a known platform-level limitation and not a regular configuration issue. +> +> Related discussions: +> - https://github.com/abpframework/abp/issues/11682 + #### Enable/Disable for Other Services Action audit logging can be enabled for any type of class (registered to and resolved from the [dependency injection](../fundamentals/dependency-injection.md)) while it is only enabled for the controllers and the application services by default. diff --git a/docs/en/modules/audit-logging-pro.md b/docs/en/modules/audit-logging-pro.md index e64b39dc66..005126d4df 100644 --- a/docs/en/modules/audit-logging-pro.md +++ b/docs/en/modules/audit-logging-pro.md @@ -73,6 +73,8 @@ You can export audit logs to Excel by clicking the "Export to Excel" button in t Entity changes tab is used to list, view and filter entity change logs. +> **Blazor Server note:** Entity change history can be missing or incomplete in some `Blazor Server` scenarios due to known SignalR/event-pipeline limitations. See [Audit Logging](../framework/infrastructure/audit-logging.md) and https://github.com/abpframework/abp/issues/11682. + ![audit-logging-module-entity-changes-list-page](../images/audit-logging-module-entity-changes-list-page.png) From bc128d46964c6187ab19df24740d39a55f0ede2e Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 10 Feb 2026 11:43:46 +0000 Subject: [PATCH 3/3] Apply code review suggestions: format links consistently and simplify note structure Co-authored-by: enisn <23705418+enisn@users.noreply.github.com> --- docs/en/framework/infrastructure/audit-logging.md | 11 +---------- docs/en/modules/audit-logging-pro.md | 2 +- 2 files changed, 2 insertions(+), 11 deletions(-) diff --git a/docs/en/framework/infrastructure/audit-logging.md b/docs/en/framework/infrastructure/audit-logging.md index b6f2ebf25d..ee2cdf7e41 100644 --- a/docs/en/framework/infrastructure/audit-logging.md +++ b/docs/en/framework/infrastructure/audit-logging.md @@ -169,16 +169,7 @@ public class HomeController : AbpController [Application service](../architecture/domain-driven-design/application-services.md) method calls also included into the audit log by default. You can use the `[DisableAuditing]` in service or method level. -> ### Blazor Server Limitation (Entity History) -> -> In `Blazor Server` applications, entity change history is currently not guaranteed to be complete for every UI interaction. -> -> Blazor Server uses SignalR-based event handling, and under some flows the audit scope/action tracking may not align with `DbContext.SaveChanges`, which can cause missing or partial entity change records. -> -> This is a known platform-level limitation and not a regular configuration issue. -> -> Related discussions: -> - https://github.com/abpframework/abp/issues/11682 +> **Blazor Server limitation (Entity history):** In `Blazor Server` applications, entity change history is currently not guaranteed to be complete for every UI interaction. Blazor Server uses SignalR-based event handling, and under some flows the audit scope/action tracking may not align with `DbContext.SaveChanges`, which can cause missing or partial entity change records. This is a known platform-level limitation and not a regular configuration issue. See [#11682](https://github.com/abpframework/abp/issues/11682) for related discussions. #### Enable/Disable for Other Services diff --git a/docs/en/modules/audit-logging-pro.md b/docs/en/modules/audit-logging-pro.md index 005126d4df..9108be0e4b 100644 --- a/docs/en/modules/audit-logging-pro.md +++ b/docs/en/modules/audit-logging-pro.md @@ -73,7 +73,7 @@ You can export audit logs to Excel by clicking the "Export to Excel" button in t Entity changes tab is used to list, view and filter entity change logs. -> **Blazor Server note:** Entity change history can be missing or incomplete in some `Blazor Server` scenarios due to known SignalR/event-pipeline limitations. See [Audit Logging](../framework/infrastructure/audit-logging.md) and https://github.com/abpframework/abp/issues/11682. +> **Blazor Server note:** Entity change history can be missing or incomplete in some `Blazor Server` scenarios due to known SignalR/event-pipeline limitations. See [Audit Logging](../framework/infrastructure/audit-logging.md) and [#11682](https://github.com/abpframework/abp/issues/11682). ![audit-logging-module-entity-changes-list-page](../images/audit-logging-module-entity-changes-list-page.png)