Hi! I'm experiencing an issue with the @freshness_policy_sensor I get

dagster_cloud_cli.core.errors.GraphQLStorageError: Error in GraphQL response: [{'message': 'User code not permitted to update asset cached status data', 'locations': [{'line': 4, 'column': 13}], 'path': ['eventLogs', 'UpdateAssetCachedStatusData']}]

on ticks. This fails even if the decorated function simply returns at once, like this:

@freshness_policy_sensor(asset_selection=AssetSelection.groups("pbi"))
def freshness_alerting_sensor(context: FreshnessPolicySensorContext):
    return

I have two assets with defined FreshnessPolicies, one of them is defined like this:

@asset(freshness_policy=FreshnessPolicy(maximum_lag_minutes=60*24*8),
       required_resource_keys={"pbi"},
       compute_kind="PBI",
       non_argument_deps={"fact_ml_olo_results",
                          "fact_bc_prices",
                          "dim_time",
                          "dim_issue",
                          "dim_publication",
                          "dim_olo_issue",
                          "dim_bc_retailer",
                          "dim_bc_issue"})
def OLO(context) -> Output:
    r = context.resources.pbi.refresh_dataset('OLO')
    return Output(r, metadata=r)

The assets work without issues. This is in Dagster Cloud.

Hi Thomas. Thanks for reporting this--this is a bug that breaks freshness policies for cron strings/time-window partitions in Cloud. We're currently working on fixing this

Great, thanks. Any chance the fix will be part of the next minor release?

This is a cloud issue, so I think it's possible for us to release it today or tomorrow. I'll keep you posted!

Ah I see, that's great!

Hi Thomas. Apologies, no github issue--but the fixes for this have already been merged. The changes will be live on the next cloud version upgrade, which I'm not entirely sure when it will happen but will happen at latest this Thursday. You'll also need to update your agent version to the latest version then