If a schedule could not be fully marked as completed, a record remained in the runningprocess table with the status "running". This blocked the ability to restart the schedule due to the presence of that "running" record. There was already a button/action available to abort the run. This action would clean up all ongoing and scheduled work items for the schedule, except for the record in the runningprocess table. This has now been adjusted so that when an abort is scheduled, the runningprocess record is also removed, allowing a new run of the schedule to be started.

Added support for webservice keys up to 255 characters