Hi, I’m trying to set up a (monthly partitioned?) asset for an API that gives me results in monthly batches. However, the data in the API has to be refreshed daily because it’s constantly being updated. My initial plan was to model this as an asset with a monthly partition definition running on a daily cron schedule but that doesn’t work because the job doesn’t try to materialise the asset as a partitioned asset. I also looked into using a freshness policy with automaterialize policy but that doesn’t seem to work for partitioned asset in a way I’d like it to work. What would be a better way to model this?

hey @Mark Nemec could you share your sensor definition?

hey @jamie I’m not using a sensor currently. Just the following asset definition

@asset(
partitions_def=MonthlyPartitionsDefinition(
        start_date="2022-01-01", timezone="America/New_York", end_offset=1
    ),
)
def invoices(…)

and schedule

daily_refresh_schedule = ScheduleDefinition(
    job=define_asset_job(
        name="invoices_job",
        selection=[invoices],
    ),
    cron_schedule="0 0 * * *",
)

cool! so is it working how you expect now or you still running into issues?

all good now