Description of problem:
When I disable a recurring logic (say, "Inventory scheduled sync", id=5), there is no way to successfully re-enable it.

WebUI offers Enable button, but it is a no-op (production.log does not log anything).

hammer does not have the capabilities to even enable or disable a recurring logic.

API does not work for me, since:

• per apidoc, "PUT /foreman_tasks/api/recurring_logics/:id" should work - but neither below command does work:

curl -H "content-type: application/json" -u admin:$PASS -X PUT -d "

" https://$(hostname -f)/foreman_tasks/api/recurring_logics/5

curl -H "content-type: application/json" -u admin:$PASS -X PUT -d "

" https://$(hostname -f)/foreman_tasks/api/recurring_logics/5

Both logs ForemanTasks::Api::RecurringLogicsController#update but with no real change.

Since WebUI disable triggered /foreman_tasks/recurring_logics/5/disable endpoint and ForemanTasks::RecurringLogicsController#disable method, I also tried:

curl -H "content-type: application/json" -u admin:$PASS -X PUT -d "

" https://$(hostname -f)/foreman_tasks/api/recurring_logics/5/enable

which failed with "No route matches" error.

So I see no way in enabling a disabled recurring logic.

Version-Release number of selected component (if applicable):
Sat 6.11

How reproducible:
100%

Steps to Reproduce:
1. Disable a recurring logic
2. Try to enable it by any mean.

Actual results:
2. No way found.

Expected results:
2. Ideally both API and WebUI does work.

Additional info: