Stay organized with collections
Save and categorize content based on your preferences.
Datagroups let you specify query caching policies and triggers for rebuilding PDTs. If you have permissions to access the Datagroups page in the Database section of the Admin panel, you'll see a summary of datagroups defined in a model for which they have data access.
Datagroup information
The Datagroups page provides the following information for each datagroup:
Column
Definition
Name
The name of the datagroup, which you define in the model file.
Label
Specifies an optional datagroup label, which you define for the datagroup parameter in the model file.
Connection
The database connection of the datagroup.
Model
The LookML model where the datagroup is defined. (Click the LookML button to open the LookML model file.)
Type
The datagroup's trigger type, such as sql_trigger or interval_trigger. If the datagroup has no specified trigger type, Type will be blank.
Description
Specifies an optional datagroup description, which you define for the datagroup parameter in the model file. The datagroup description can be used to explain the datagroup's purpose and mechanism.
Depending on the datagroup status, the following detailed information may also appear under the name:
Status shows the current status of the datagroup. The status is also indicated by the colored dots next to each line for the datagroup:
Green — The datagroup is in a ready state.
Orange — The datagroup is in the triggered state, or the datagroup was recently deployed to production and the trigger check cycle has not yet started.
Red — The most recent trigger check errored, or there is an error with the datagroup's LookML. You can click the LookML button to open the LookML model file.
Trigger value shows the result of the sql_trigger query that triggered the datagroup. For example, if a datagroup uses a SQL trigger based on the maximum ETL log ID, the Trigger value would show the new ETL log ID that triggered the datagroup.
Triggered since is displayed for datagroups in the triggered state to show how long it has been since the datagroup was triggered. This provides information on how long it is taking to rebuild PDTs and run the queries that triggered by the datagroup. Once all PDTs are rebuilt, the datagroup's color will update to green to indicate that the datagroup is ready, and after several minutes the Triggered since information will disappear from the page since the datagroup is complete.
Trigger error provides error information for the datagroup triggers, such as a syntax error in the datagroup's SQL trigger. When you see an error, you can click the LookML button to open the LookML model file and correct the SQL syntax.
Trigger last checked shows the last time that the datagroup's sql_trigger SQL query was run. If the value returned by the query is different next time, that triggers the datagroup.
Cache reset at shows the time when the cache was last reset (when the cached data in the datagroup was last invalidated).
Click the LookML button to open the LookML model file where the datagroup is defined.
Select Reset Cache from the gear menu settings to immediately invalidate the cached results for all Explores using that datagroup.
Select Trigger Datagroup from the gear menu settings to invalidate the cached results for all Explores and rebuild all PDTs using that datagroup. The PDT rebuild will begin based on the next time specified in the connection's PDT and Datagroup Maintenance Schedule field, such as every five minutes. Any scheduled data deliveries of Looks, dashboards, and LookML dashboards that use the datagroup as a trigger will be sent when the triggered datagroup reaches the ready state.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[],[],null,["# Admin settings - Datagroups\n\n[Datagroups](/looker/docs/2512/caching-and-datagroups#specifying_caching_policies_with_datagroup_parameters) let you specify query caching policies and triggers for rebuilding PDTs. If you have [permissions to access the **Datagroups** page](/looker/docs/2512/admin-panel-users-roles#see_datagroups) in the **Database** section of the Admin panel, you'll see a summary of datagroups defined in a model for which they have [data access](/looker/docs/2512/access-control-and-permission-management#controlling_feature_and_data_access).\n| **Note:** If you have a permission that provides access to only select pages in the Admin panel, such as [`manage_schedules`](/looker/docs/2512/admin-panel-users-roles#manage_schedules), [`manage_themes`](/looker/docs/2512/admin-panel-users-roles#manage_themes), or [`see_admin`](/looker/docs/2512/admin-panel-users-roles#see_admin), but you don't have the [Admin role](/looker/docs/2512/admin-panel-users-roles#default_roles), the page or pages that are described here may not be visible to you in the Admin panel.\n\nDatagroup information\n---------------------\n\nThe **Datagroups** page provides the following information for each datagroup:\n\nDepending on the datagroup status, the following detailed information may also appear under the name:\n\n\u003cbr /\u003e\n\n- **Status** shows the current status of the datagroup. The status is also indicated by the colored dots next to each line for the datagroup:\n - **Green** --- The datagroup is in a ready state.\n - **Orange** --- The datagroup is in the triggered state, or the datagroup was recently deployed to production and the trigger check cycle has not yet started.\n - **Red** --- The most recent trigger check errored, or there is an error with the datagroup's LookML. You can click the **LookML** button to open the LookML model file.\n- **Trigger value** shows the result of the [`sql_trigger`](/looker/docs/2512/reference/param-model-datagroup#sql_trigger) query that triggered the datagroup. For example, if a datagroup uses a SQL trigger based on the maximum ETL log ID, the **Trigger value** would show the new ETL log ID that triggered the datagroup.\n- **Triggered since** is displayed for datagroups in the triggered state to show how long it has been since the datagroup was triggered. This provides information on how long it is taking to rebuild PDTs and run the queries that triggered by the datagroup. Once all PDTs are rebuilt, the datagroup's color will update to green to indicate that the datagroup is ready, and after several minutes the **Triggered since** information will disappear from the page since the datagroup is complete.\n- **Trigger error** provides error information for the datagroup triggers, such as a syntax error in the datagroup's SQL trigger. When you see an error, you can click the **LookML** button to open the LookML model file and correct the SQL syntax.\n- **Trigger last checked** shows the last time that the datagroup's `sql_trigger` SQL query was run. If the value returned by the query is different next time, that triggers the datagroup.\n- **Cache reset at** shows the time when the cache was last reset (when the cached data in the datagroup was last invalidated).\n\n\u003cbr /\u003e\n\nDatagroup actions\n-----------------\n\nIf you have the [necessary permissions for updating datagroups](/looker/docs/2512/admin-panel-users-roles#update_datagroups), you can perform the following actions on datagroups from the **Datagroups** Admin page:\n\n1. Click the **LookML** button to open the LookML model file where the datagroup is defined.\n2. Select **Reset Cache** from the gear menu settings to immediately invalidate the cached results for all Explores using that datagroup.\n3. Select **Trigger Datagroup** from the gear menu settings to invalidate the cached results for all Explores and rebuild all PDTs using that datagroup. The PDT rebuild will begin based on the next time specified in the connection's [**PDT and Datagroup Maintenance Schedule**](/looker/docs/2512/connecting-to-your-db#pdt_maintenance_schedule) field, such as every five minutes. Any scheduled data deliveries of [Looks](/looker/docs/2512/delivering-looks-explores#specifying_the_datagroup_trigger), [dashboards](/looker/docs/2512/scheduling-and-sending-dashboards#schedules_triggered_by_datagroup_updates), and [LookML dashboards](/looker/docs/2512/scheduling-and-sending-dashboards#schedules_triggered_by_datagroup_updates) that use the datagroup as a trigger will be sent when the triggered datagroup reaches the ready state."]]