This is a common limitation when using workflows with DataGrid2. Workflows run outside of the page context, so the UI is not automatically aware that something has changed. That’s why you only see the updated status after manually refreshing the page.

Because of this, DataGrid2 will not refresh on its own unless something in the page context is updated. Calling a workflow directly from a button does not trigger any UI refresh.

A clean approach is to wrap the workflow call inside a microflow. In this microflow, you trigger the workflow and then refresh something that the page depends on. This could be the main object or a helper object.

If your datagrid is using a datasource microflow, make sure that datasource depends on something you can refresh. For example, a non-persistent helper entity. After the workflow execution, you update this object and use “Refresh in client” so the grid is forced to reload.

This way, you avoid using timers and keep the behavior predictable.

In short, workflows do not trigger UI updates automatically, so you need to refresh the page context (via microflow or helper object) to make DataGrid2 reload.

 If this resolves your issue, please mark it as accepted.

SImilar to previous post, I always use a Change Object activity in the microflow, where I change the object that the datagrid2 is working with, and then set that activity to refresh only and not commit of course.

Joe,

One other suggestion: Data Grid 2 has a property called Refresh Time (in seconds) that is used to refresh data in Data Grid 2 without any other work required. By default, this setting is 0 which means no auto refresh happens. However, setting it to a reasonable value will refresh the data automatically. This will update the data on your page periodically based on workflow updates.

Hope that helps,

Mike