NotSupportedException in AwaitingJobsPage

bug?
1

I am using the new version 1.5.0 with the Firebird Storage 1.3.4. The most of HF works as expected. But the new Page: Awaitng Jobs returns with an Exception.

The “Retries” Page handle the Error in a better way:
Message:
Retries are working, but this page can’t be displayed
Don’t worry, retries are fully supported. Your current job storage does not fully support some queries required to show this page. Please try to update your storage or wait until the full command set is implemented.
Please go to the Scheduled jobs page to see all the scheduled jobs including retries.

[NotSupportedException: Continuations are not supported for your current job storage implementation.]
Hangfire.Dashboard.Pages.AwaitingJobsPage.Execute() +332
Hangfire.Dashboard.RazorPage.TransformText(String body) +41
Hangfire.Dashboard.RazorPageDispatcher.Dispatch(RequestDispatcherContext context) +239
Hangfire.Dashboard.DashboardMiddleware.Invoke(IOwinContext context) +582
Microsoft.Owin.Mapping.d__0.MoveNext() +594
System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +144
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +84
Microsoft.Owin.Host.SystemWeb.IntegratedPipeline.d__5.MoveNext() +291
System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +144
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +84
Microsoft.Owin.Mapping.d__0.MoveNext() +1178
System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +144
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +84
Microsoft.Owin.Host.SystemWeb.IntegratedPipeline.d__5.MoveNext() +291
System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +144
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +84
Microsoft.Owin.Host.SystemWeb.IntegratedPipeline.d__2.MoveNext() +293
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() +32
Microsoft.Owin.Host.SystemWeb.IntegratedPipeline.IntegratedPipelineContext.EndFinalWork(IAsyncResult ar) +208
System.Web.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +443
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +288

2

@Flyff_Sebulba, thank you for the tip! I’ve already fixed this, changes will be shipped with upcoming 1.5.1.

3

Thank you.
Please keep in mind, The supported Job Store in the Page is only the SQL Jobstore.

using (var connection = Storage.GetConnection())
{
var storageConnection = connection as JobStorageConnection;

    if (storageConnection != null)
    {
        pager = new Pager(from, perPage, storageConnection.GetSetCount("awaiting"));
        jobIds = storageConnection.GetRangeFromSet("awaiting", pager.FromRecord, pager.FromRecord + pager.RecordsPerPage - 1);
    }
}

I tried to fix it with:

using (var connection = Storage.GetConnection())
{
    errorConnection = (connection == null);
    if (errorConnection == false)
    {
        var items = connection.GetAllItemsFromSet("awaiting");
        pager = new Pager(from, perPage, items.Count);
        var result = (from rs in items select rs).Skip(pager.FromRecord).Take(pager.RecordsPerPage);
        jobIds = result.ToList();
    }
}