Skip to content

manually removed partition causes a graphql error on downstream assets automation tab #33910

Description

@markbaas

What's the issue?

Description:
Our setup is as following:

  • extract assets on a daily basis copy data from external systems into our bronze layer they then create a dynamic partition record
  • load assets use that partition definition and load the data in our dwh
  • dagster dbt models that data

When an extract fails the load will become invalid which then doesnt trigger a dbt run. So to make everything "green" again I delete the failed partition. This then causes en error on the automation tab of downstream dbt models.

Dagster version 1.11 - 13.6

Error message:
I removed a failed partition in the ui and then in the downstream assets I get an error on the automation tab: Operation name: {GetEvaluationsQuery}

Message: Partition range 2026/06/04/051925 | incremental to 2026/06/04/051925 | incremental is
not a valid range. Nonexistent partition keys:
['2026/06/04/051925 | incremental']

Path: ["assetConditionEvaluationRecordsOrError"]

Locations: [{"line":18,"column":3}]

Stack Trace:
File "/usr/local/lib/python3.12/site-packages/graphql/execution/execute.py", line 523, in execute_field
result = resolve_fn(source, info, **args)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/dagster_graphql/schema/roots/query.py", line 1312, in resolve_assetConditionEvaluationRecordsOrError
return fetch_asset_condition_evaluation_records_for_asset_key(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/dagster_graphql/implementation/fetch_asset_condition_evaluations.py", line 134, in fetch_asset_condition_evaluation_records_for_asset_key
return _get_graphene_records_from_evaluations(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/dagster_graphql/implementation/fetch_asset_condition_evaluations.py", line 45, in _get_graphene_records_from_evaluations
GrapheneAssetConditionEvaluationRecord(evaluation) for evaluation in evaluation_records
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/dagster_graphql/schema/asset_condition_evaluations.py", line 356, in init
evaluation=GrapheneAssetConditionEvaluation(root_evaluation),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/dagster_graphql/schema/asset_condition_evaluations.py", line 217, in init
GrapheneUnpartitionedAssetConditionEvaluationNode(evaluation)
File "/usr/local/lib/python3.12/site-packages/dagster_graphql/schema/asset_condition_evaluations.py", line 52, in init
if evaluation.true_subset.size > 0:
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/dagster/_core/asset_graph_view/serializable_entity_subset.py", line 129, in size
return len(self.subset_value)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/dagster/_core/definitions/partitions/context.py", line 82, in wrapper
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/dagster/_core/definitions/partitions/subset/key_ranges.py", line 82, in len
len(self.partitions_definition.get_partition_keys_in_range(partition_key_range))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/dagster/_core/definitions/partitions/definition/partitions_definition.py", line 109, in get_partition_keys_in_range
raise DagsterInvalidInvocationError(

What did you expect to happen?

See the automation tab loaded so I can debug automation conditions.

How to reproduce?

  1. remove a dynamic partition
  2. go to downstream asset automation tab

Dagster version

1.13.7

Deployment type

Other

Deployment details

It runs within azure container instances.

Additional information

No response

Message from the maintainers

Impacted by this issue? Give it a 👍! We factor engagement into prioritization.

Metadata

Metadata

Assignees

No one assigned

    Labels

    type: bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions