hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-12-14 17:02:49 +03:00
Code Issues Projects Releases Wiki Activity

Hasura Cloud Document change for scheduled triggers data retention period

Browse Source 
>

## 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
This commit is contained in:
Poojan Savani 2022-08-23 13:09:44 +05:30 committed by hasura-bot
parent 2120c601d3
commit fc97c8e456
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/docs/scheduled-triggers/clean-up.mdx
View File

@ -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: