Scoped dependency injection in a scheduled task

since they make use of Xperience system services that are also scoped.

All of Xperience's services are registered as singleton or transient - so if you are using Scope services that's because your application needs it, not because you are injecting scoped dependencies from Xperience.

That's a problem here because the scheduled tasks don't run in a scoped context.

Like you mentioned, you can always generate your own scope if you really need one. You lose the benefit of constructor injection into the scheduled task, but you can then handle any scoped services you need.

public class HelloScheduledTask : IScheduledTask
{
    private readonly IServiceProvider provider;

    public HelloScheduledTask(IServiceProvider provider)
    {
        this.provider = provider;
    }

    // Called by the system when running the scheduled task.
    public Task<ScheduledTaskExecutionResult> Execute(ScheduledTaskConfigurationInfo task, CancellationToken cancellationToken)
    {
        using var scope = provider.CreateScope();

        var service = scope.ServiceProvider.GetRequiredService<MyScopedService>();

        // use your service

        return Task.FromResult(ScheduledTaskExecutionResult.Success);
    }
}

but it seems like tasks should just run in their own DI scope.

Scheduled tasks are managed by an CMS.DataEngine.ApplicationBackgroundService, so it should be possible to have it generate a new scope for each task execution. I'm guessing we didn't do this because it was a much simpler solution to instantiate the scheduled tasks as transient and not have to handle creating/disposing of scopes.

If you want to share your use-cases you can give us some feedback on the roadmap.