Hi Dagster we ve just set up a multi asset sensor but we re

Question

Hi Dagster we ve just set up a multi asset sensor but we re getting this error see thread thread

Jamie Lee · Answer

```dagster core errors SensorExecutionError Error occurred during the execution of evaluation fn for sensor trigger main pipeline on prod dms File usr local lib python3 8 site packages dagster grpc impl py line 324 in get external sensor execution return sensor def evaluate tick sensor context File usr local lib python3 8 contextlib py line 131 in exit self gen throw type value traceback File usr local lib python3 8 site packages dagster core errors py line 206 in user code error boundary raise error cls The above exception was caused by the following exception AttributeError int object has no attribute items File usr local lib python3 8 site packages dagster core errors py line 199 in user code error boundary yield File usr local lib python3 8 site packages dagster grpc impl py line 324 in get external sensor execution return sensor def evaluate tick sensor context File usr local lib python3 8 site packages dagster core definitions sensor definition py line 425 in evaluate tick result = list self evaluation fn context File usr local lib python3 8 site packages dagster core definitions sensor definition py line 594 in wrapped fn for item in result File usr local lib python3 8 site packages dagster core definitions multi asset sensor definition py line 1101 in fn multi asset sensor context = MultiAssetSensorEvaluationContext File usr local lib python3 8 site packages dagster annotations py line 123 in init undecorated init self args kwargs File usr local lib python3 8 site packages dagster core definitions multi asset sensor definition py line 253 in init self unpacked cursor = MultiAssetSensorContextCursor cursor self File usr local lib python3 8 site packages dagster core definitions multi asset sensor definition py line 128 in init for str asset key cursor list in loaded cursor items ```

Nicolas Parot Alvarez · Answer

Same for me just had it with latest Dagster 1 1 8

Nicolas Parot Alvarez · Answer

Strangely I can t reproduce it with a simple example ```from dagster import multi asset sensor RunRequest AssetSelection asset define asset job Definitions asset def asset1 return 1 2 3 asset def asset2 asset1 return asset1 + 4 asset def asset3 asset2 return asset2 + 4 my job12 = define asset job name= j12 selection=AssetSelection assets asset1 asset2 my job3 = define asset job name= j3 selection=AssetSelection assets asset3 multi asset sensor asset selection=AssetSelection assets asset1 asset2 job=my job3 def asset 1 and 2 sensor context asset events = context latest materialization records by key if all asset events values context advance all cursors return RunRequest defs = Definitions assets= asset1 asset2 asset3 jobs= my job12 my job3 sensors= asset 1 and 2 sensor ```

sandy · Answer

< claire> < jamie> it sounds like the multi asset sensor cursor is an integer when Dagster expects it to be a dict Is it possible this is a backwards compatibility issue where it used to be an int and we changed it to a dict

claire · Answer

I don t believe the multi asset sensor ever stored an `int` cursor My guess about what s happening is you had some other type of sensor i e an asset sensor that had the same name as your multi asset sensor When dagster attempts to read the cursor from storage that cursor will be your asset sensor cursor instead of a new cursor You could fix this by renaming your sensor to something new and unused or you could reset the cursor ```dagster sensor cursor delete```

Jamie Lee · Answer

Ah yes that is exactly it Thank you

Jamie Lee · Answer

I deleted the cursor value in dagit and turned the sensor and on and off and it created the correct cursor value for me +1