What causes EVENT_TABLE_NOT_FOUND?

The event table was dropped or never created before enabling logging or tracing on a function or procedure. The account-level EVENT_TABLE parameter points to a table that no longer exists. The calling role lacks SELECT or INSERT privilege on the event table. A task or alert is configured to write to the default SNOWFLAKE.TELEMETRY.EVENTS view but the role has not been granted the required system privilege

How do I fix EVENT_TABLE_NOT_FOUND?

Step 1: Run SHOW PARAMETERS LIKE 'EVENT_TABLE' IN ACCOUNT to see the current event table configuration.. Step 2: Verify the event table exists by querying INFORMATION_SCHEMA.TABLES in the target database.. Step 3: If missing, create a new event table using CREATE EVENT TABLE . . and set it at the account level with ALTER ACCOUNT SET EVENT_TABLE.. Step 4: Grant the required privileges: SELECT on the event table for readers, and for system access to SNOWFLAKE.TELEMETRY.EVENTS, grant the SNOWFLAKE.TELEMETRY_VIEWER database role.. Step 5: Re-enable logging on affected functions or procedures using ALTER FUNCTION SET LOG_LEVEL.

Medium severityconfiguration

Power BI Refresh Error:
EVENT_TABLE_NOT_FOUND

What does this error mean?

A logging, tracing, or alert operation failed because the Snowflake event table configured at the account, database, or object level does not exist or is not accessible to the current role.

Common causes

1The event table was dropped or never created before enabling logging or tracing on a function or procedure
2The account-level EVENT_TABLE parameter points to a table that no longer exists
3The calling role lacks SELECT or INSERT privilege on the event table
4A task or alert is configured to write to the default SNOWFLAKE.TELEMETRY.EVENTS view but the role has not been granted the required system privilege

How to fix it

1Step 1: Run SHOW PARAMETERS LIKE 'EVENT_TABLE' IN ACCOUNT to see the current event table configuration.
2Step 2: Verify the event table exists by querying INFORMATION_SCHEMA.TABLES in the target database.
3Step 3: If missing, create a new event table using CREATE EVENT TABLE <db>.<schema>.<name> and set it at the account level with ALTER ACCOUNT SET EVENT_TABLE.
4Step 4: Grant the required privileges: SELECT on the event table for readers, and for system access to SNOWFLAKE.TELEMETRY.EVENTS, grant the SNOWFLAKE.TELEMETRY_VIEWER database role.
5Step 5: Re-enable logging on affected functions or procedures using ALTER FUNCTION SET LOG_LEVEL.

Frequently asked questions

Can I have multiple event tables for different schemas in Snowflake?

Yes. You can configure an event table at the account, database, or schema level. Object-level settings override account-level ones, allowing different environments to write to separate event tables.

How long is data retained in a Snowflake event table?

By default, event tables use the standard Snowflake data retention policy (0 to 90 days, configurable). There is no system-enforced retention limit specifically for event tables — standard Time Travel and data retention settings apply.