Discussion about IInvocable and ICancellableInvocable design.

[PhilApps]

Hi,
I discovered Coravel recently and I especially like the ability to tell different kinds of tasks not to run at the same time, quartz is currently unable to do this, or with much more programming efforts.
But now, I have a concern about IInvocable and ICancellableInvocable design. I find it quite weird and also quite cumbersome that we have to always implement the "CancellationToken" member for each cancellable task. In addition, the interface exposes a setter of the cancellation token member which I don't like that much.
So my question is: why not simply have just one interface "IInvocable" with an "Invoke" member taking a "CancellationToken" parameter? I find it way simpler. Like this :

public interface IInvocable
{
    Task Invoke(CancellationToken cancellationToken);
}

What do you think about it ?