Version Information

Server Version: v2.1.1
CLI Version (for CLI related issue): v2.1.1

This also occurs in v2.1.0-beta.3.

Environment

Docker (hasura/graphql-engine:v2.1.1.cli-migrations-v3)

Confirmed using both MacOS Monterey and CentOS Linux release 7.9.2009.

What is the expected behaviour?

Cron triggers added without selecting "Include in Metadata" should be visible on the cron trigger management page at /events/cron/manage.

Keywords

cron, cron trigger, metadata

What is the current behaviour?

Only cron triggers included in metadata are shown.

I can confirm that the created cron trigger exists in the "hdb_catalog" metadata table after creation and the trigger still runs.

Modifying the metadata directly in the database and changing "include_in_metadata" to true causes the cron trigger to appear on the management page after reloading.

Unchecking "Include in Metadata" in the console for an existing trigger and submitting the change immediately causes the trigger to disappear from the management page.

I believe this issue may have appeared after upgrading from v2.0.10 to v2.1.0-beta.3.

How to reproduce the issue?

1. Create a cron job without selecting "Include in Metadata".
2. Notice the job does not appear on the cron trigger management page.
3. Try to create a job with the same name again.
4. Notice you get an error saying the job already exists.

Screenshots or Screencast

None

Please provide any traces or logs that could help here.

No errors are shown in the console.

Any possible solutions?

I hope so.

Can you identify the location in the source code where the problem exists?

No

If the bug is confirmed, would you be willing to submit a PR?

No. I'm not familiar with the codebase.