Hi ! Previously, I was using a schedule to trigger...
# ask-community
Hi ! Previously, I was using a schedule to trigger a job. I decided to replace this schedule by a sensor using the same name. I have the impression that the dagster DB still considers it a schedule since when I modify the cursor I get the following error:
Copy code
AttributeError: 'ScheduleInstigatorData' object has no attribute 'last_tick_timestamp'
  File "/usr/local/lib/python3.8/site-packages/dagster_graphql/implementation/utils.py", line 101, in _fn
    return fn(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/dagster_graphql/implementation/fetch_sensors.py", line 226, in set_sensor_cursor
Is there a way to fix this without having to define a new name for the sensor?
I had reported this a while ago, but don’t think it’s fixed yet. How comfortable are you with database queries? If you delete a few things from the dagster database manually, it can be worked around
Ah found some bug for it: https://github.com/dagster-io/dagster/issues/7349, https://github.com/dagster-io/dagster/issues/7018 Cc @chris - if memory serves correct, you had reproduced this for the schedule -> sensor case too
Anyways, if you’re comfortable with queries there are two things in the database that’ll need to be cleaned up. I can dig up the queries in a bit when I’m in front of my laptop. Let’s just say I’ve used them quite a bit…(I’ve run into this many times)
yep I believe I repro'd this a while back. We haven't prioritized a fix yet unfortunately. @Adam Bloom if you have the time, could be nice to put those queries either onto the github issue or into a github discussion, I'm sure folks run into this problem pretty often at some level
I can definitely do that later today. I couldn't remember if we opened an issue earlier or not - sounds like create a new one and link these?
Thanks for your help. I will try this 😉