Data Source refresh stuck in queued state #15036
Replies: 4 comments 2 replies
-
I fixed it in nbshell:
|
Beta Was this translation helpful? Give feedback.
-
Has anyone else run into this? I just got it whilst testing Data Sources. |
Beta Was this translation helpful? Give feedback.
-
Not sure if it can help, but on our side, we observed that issue when we had scripts from our datasource that were being executed. |
Beta Was this translation helpful? Give feedback.
-
had a similar issue we were doing mass updates which triggered an event rule which we were testing. Way i cleared it was doing it the dirty way on redis itself.
copilot had said to do this |
Beta Was this translation helpful? Give feedback.
-
One of my local data sources got stuck in the Queued state when I tried to sync it today, so now I'm unable to click the sync button (it's grayed out). I've used the sync feature dozens of times before so I'm not sure why it happened this time. There are no pending or running jobs showing in
/core/data-sources/1/jobs/
or/core/jobs/
.I've tried restarting the service with
systemctl restart netbox netbox-rq
. How can I fix this?Beta Was this translation helpful? Give feedback.
All reactions