Removing job from recurring.yml does not remove job from recurring tasks tab in mission control
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start with config/recurring.yml and the SolidQueue::RecurringTask.static entry point, then review the behavior introduced by change #433. Reproduce by removing or commenting out the development job, restarting Solid Queue, and checking both recurring tasks in Mission Control and the static task list; done means the removed job no longer appears.
Written by the indexing model from the issue text.
Description
I'm testing a recurring job in development which works fine but when I comment it out or remove it from recurring.yml and restart the system, it still appears in the recurring tasks tab of mission control. From my understanding it should be removed especially with this change #433? I still see the job when I run SolidQueue::RecurringTask.static
We are new to solid_queue so we may have set something up incorrectly. We are using v1.2.1 and Rails 7.1.5.1. We are using the single database configuration and starting solid_queue with foreman (didnt set up the puma plugin).
# config/recurring.yml
production:
stats_import_yesterday_job:
class: StatsImportYesterdayJob
schedule: "at 12:05am every day"
staging:
stats_import_yesterday_job:
class: StatsImportYesterdayJob
schedule: "at 12:05am every day"
dev:
stats_import_yesterday_job:
class: StatsImportYesterdayJob
schedule: "at 12:05am every day"
#development:
# stats_import_yesterday_job:
# class: StatsImportYesterdayJob
# schedule: "every minute"
- Dominant language
- Ruby
- Stars
- 2.5k
- Forks
- 250
- Avg merge
- 7h 7m
- Merged PRs (30d)
- 6
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rails/solid_queue
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
rails/solid_queue#802 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
rails/solid_queue#797 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
rails/solid_queue#792 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
rails/solid_queue#780 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
rails/solid_queue#621 · 3 comments · 6 reactions ·
All issues in rails/solid_queue
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
バグ
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
voxpupuli/puppet-epel#186 · 1 comment ·