In 15.26 we will be expanding the capabilities of the Queued Tasks API to include queuing result quality tuning runs. This is to allow System Administrators running multi tenanted instances of Funnelback to manage when tuning runs commence.
Where no queue management has been put in place, tuning runs triggered via the Queued Tasks API will commence immediately. This behaviour mimics that of the Tuning API.
As the Queued Tasks API provides the existing Tuning API behaviour as well as the new queuing capability we will also be removing the Tuning API in 15.26.
We do not expect the decision to remove the Tuning API will cause any issues as we do not believe it has been in use. If you believe this is not the case and there are valid reasons for us retaining the Tuning API please let me know.
If we have not heard back from anyone by COB on the 18th November then we will proceed as planned.