Skip to content

HasPendingInteruptions returns incorrect value in Octopus Clients #10214

Description

@benPearce1

Severity

Blocking some customers

Version

Client version 20.13 or later with Server 2025.4 or earlier

Latest Version

I could reproduce the problem in the latest build

What happened?

A change to the task resource in Octopus Client always set the value of HasPendingInteruptions to false.

Reproduction

Using a 2026.1.419 or earlier server with a client version of 20.13.2583 or later.
View a task that has a pending interruption, such as a manual intervention.
The response over the API (as viewed through browser dev tools), will have the HasPendingInteruptions value set correct.
Fetching the same task by Id using the client: client.Tasks.Get("ServerTasks-123") will always have the HasPendingInteruptions set to false.

Error and Stacktrace

More Information

This is due to the client calculating the value for HasPendingInteruptions from the PendingInteruptionTypes collection property

public bool HasPendingInterruptions => PendingInterruptionTypes.Count > 0;

The PendingInteruptionTypes property is not returned by server versions 2026.1.419 and earlier, so this is collection in the TaskResource is always empty.

Workaround

Use an earlier version of the client library.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugThis issue represents a verified problem we are committed to solving

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions