@Alper will look into but worst case you
@Alper will look into but worst case you can do directly in the db at v2_job_queue
12 Replies
can i just delete entries in that table, even if running = true?
no need to update other tables?
well if they're in the wrong workspace_id
i have 800+ entries in there btw and all have the correct workspace id (so not sure where the reported bug comes from)
did you refresh the page after renaming the workspace?
yes. renaming was a few days ago
but i have pending jobs from up to december
I don't understand, do they all have the correct workspace_id or do you have pending jobs from up to december?
they all have the correct workspace id which is "goodwatch". before that it was "flickvibe"
and as you can see the oldest entries are from december
so I don't understand, the UI showed you goodwatch and you said it was correct
so why is it highlighted in red in your picture?
the important red highlight is "0 jobs" because i assumed it should be all 514 that are visible with the current filter
i highlighted the workspace id as well because i thought there would be "flickvibe" entries in the job queue, but that was a false assumption - so that highlight is pointless
also, how is it possible that something is running but has not started? (only have 2 of those entries)
It's because of the migration but it's harmless