- 🇬🇧United Kingdom alexpott 🇪🇺🌍
As this feature request has not received any support or work for nearly 8 years I'm closing this. one.
There are a number of scenarios I've recently run into where I want jobs to be not-processed but also not-deleted. Specifically situations like this:
* An issue where a certain subtype of job was being handled improperly... so the queues were stopped, batch generators run, and then the status column was updated manually to a value that wasn't -1, 0, 1, or 2. Then the queues got started back up.
* Copying a database over to a non-production environment and I want the jobs that are not processed to be maintained but just not run for debugging purposes.
So I'd like to propose adding a new status ADVANCEDQUEUE_STATUS_HELD with a value of -2. Previously I had used 3 but positive numbers generally seem to indicate that the job has already ran. A negative number would point to the fact that the job hasn't been run.
Patch pending.
Closed: outdated
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
As this feature request has not received any support or work for nearly 8 years I'm closing this. one.