From fc97c8e45658754a744c65fe54bac868082ba6a7 Mon Sep 17 00:00:00 2001 From: Poojan Savani Date: Tue, 23 Aug 2022 13:09:44 +0530 Subject: [PATCH] Hasura Cloud Document change for scheduled triggers data retention period MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit > ## Description ✍️ Hasura cloud each for each project retention period for hdb_cron_events and hdb_cron_event_invocation_logs tables is 1 month. which means that for any project in hasura cloud the user can only look at the past 1 month of data of Cron triggers. ### Catalog upgrade ✍ Does this PR change Hasura Catalog version? - ❎ No ### Metadata ✍ Does this PR add a new Metadata feature? - ❎ No ### GraphQL ✍ - ✅ No new GraphQL schema is generated ### Breaking changes ✍ - ✅ No Breaking changes --- #### Commit title Hasura Cloud Document change for scheduled triggers data retention period PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5566 Co-authored-by: Sean Park-Ross <94021366+seanparkross@users.noreply.github.com> GitOrigin-RevId: 751e544a0add51c5be6ad5c8e6b86624604b93eb --- docs/docs/scheduled-triggers/clean-up.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/docs/scheduled-triggers/clean-up.mdx b/docs/docs/scheduled-triggers/clean-up.mdx index e116ec4e4b0..9c850d1a7ba 100644 --- a/docs/docs/scheduled-triggers/clean-up.mdx +++ b/docs/docs/scheduled-triggers/clean-up.mdx @@ -19,6 +19,12 @@ Hasura stores event data associated with scheduled triggers in **the "hdb_catalo If there are lots of events, the events tables can get huge and you may want to prune them. You can use any of the following options to prune your event data depending on your need. +:::info Note + +For each project in Hasura Cloud the retention period for cron events and invocation logs for cron triggers is 1 month. + +::: + ## Tables involved Cron triggers have two tables managed by Hasura: