"When does a ""missing"" Agent status re-sync after Agent OS reboot ?"



1 comment

  • Avatar

    Basically your restart of the Go agent service fixed it.

    You can make the Go agent service startup type to be "Automatic (Delayed Start)" and see if such a thing happens again on agent reboot.

    The cancellation of the queued up pipelines was not necessary.

Please sign in to leave a comment.