Pending Review
Last Updated:
27 Jul 2026 06:12
by Chethan
Chethan
Created on:
27 Jul 2026 06:12
Category:
Grid
Type:
Bug Report
Telerik MVC Grid: Multiple Ajax requests triggered when changing page size
Hello Telerik Support Team,
We are experiencing an issue with a Telerik MVC Grid where changing the page size results in multiple Ajax requests being sent to the server.
Environment
- Telerik MVC Grid
- ASP.NET MVC
- Ajax Binding Enabled
- Custom Binding Enabled
Current Behavior
When the user changes the page size (for example, from 5 to 50), multiple requests are sent to the grid's Ajax binding action.
Example:
- Grid displays 5 rows.
- User changes page size from 5 to 50.
- Multiple requests are observed in the browser Network tab.
- All requests target the same Ajax binding action.
- All requests return HTTP 200.
Expected Behavior
Changing the page size should trigger a single Ajax request to the server.The grid uses below code
pager.PageSize(Model.GridModel.PageSize, Model.GridModel.PageSizeSelections)
.Position(GridPagerPosition.Bottom)
.Style(GridPagerStyles.NextPreviousAndNumeric | GridPagerStyles.PageInput | GridPagerStyles.PageSizeDropDown))
.NoRecordsTemplate(TMS.Resources.PositionManager.UI.NoOnboardingDocumentInstancesFoundMessage)
.HtmlAttributes(new { width = "98%" })
- Is multiple Ajax-request behavior during page-size changes a known Telerik MVC Grid issue or expected behavior?
- Are there Telerik recommendations to prevent duplicate Ajax requests when changing page size?
- Is there a built-in Telerik mechanism to ensure only a single Ajax request is sent for a page-size change?
- Could this be caused by Telerik internally triggering multiple rebind operations?
- Is there a Telerik-supported approach for preventing duplicate requests without introducing a custom client-side request lock?
We also found a Telerik forum post discussing similar behavior during page-size changes:
https://www.telerik.com/forums/multiple-requests-on-telerik-grid-page-size-change
Could you please confirm whether our observed behavior is related to the same issue and advise on the recommended solution?
Note:
This issue occurs in a legacy ASP.NET MVC application using Telerik Extensions for ASP.NET MVC version 2011.3.1306.340 running on .NET Framework (not .NET 6+).
Indicators:
- .ascx ViewUserControl views
- System.Web.Mvc
- Telerik MVC Extensions (legacy Telerik MVC Grid)
Thank you.
0 comments