State management for device-driven management workflows

1. A system comprising:

a computing device comprising a processor and a memory; and

machine-readable instructions stored in the memory that, when executed by the processor, cause the computing device to at least:

perform a first execution of a device-driven management workflow, wherein the device-driven management workflow comprises one or more branch sequences that are configured to be executed based at least in part on a state of the computing device and wherein the first execution of the device-driven management workflow executes at least a first branch sequence of the one or more branch sequences;

evaluate the computing device to determine a current state of the computing device;

compare the current state of the computing device to an expected state of the computing device, wherein the expected state of the computing device is based at least in part on a result of the first execution of the device-driven management workflow by the computing device; and

in response to a determination that the current state of the computing device fails to match the expected state of the computing device, perform a second execution of the device-driven management workflow, wherein the second execution of the device-driven management workflow executes at least a second branch sequence of the one or more branch sequences based at least in part on the current state of the computing device.

2. The system of claim 1 , wherein the machine-readable instructions, when executed by the processor, further cause the computing device to at least:

determine that the second execution of the device-driven management workflow failed; and

send an error message to a management service, the error message comprising an indication that the second execution of the device-driven management workflow failed.

3. The system of claim 2 , wherein the machine-readable instructions that, when executed by the processor, cause the computing device to at least determine that the second execution of the device-driven management workflow failed, further cause the computing device to at least:

reevaluate the computing device to determine the current state of the computing device;

compare the current state of the computing device to the expected state of the computing device; and

determine, based at least in part on a comparison of the current state of the computing device to the expected state of the computing device, that the second execution of the device-driven management workflow failed.

4. The system of claim 1 , wherein the machine-readable instructions that, when executed by the processor, cause the computing device to determine that the current state of the computing device fails to match the expected state of the computing device, further cause the computing device to at least:

identify a current version of a resource installed on the computing device;

compare the current version of the resource to a version of the resource specified by the device-driven management workflow; and

determine that the current version of the resource is less than the version of the resource specified by the device-driven management workflow.

5. The system of claim 1 , wherein the machine-readable instructions that, when executed by the processor, cause the computing device to determine that the current state of the computing device fails to match the expected state of the computing device, further causes the computing device to at least determine that the device-driven management workflow has failed to previously successfully execute to completion.

6. The system of claim 1 , wherein the machine-readable instructions, when executed by the processor, further cause the computing device to at least:

monitor execution of individual tasks of the device-driven management workflow; and

report the execution of the individual tasks of the device-driven management workflow to a management service.

7. The system of claim 1 , wherein the machine-readable instructions, when executed by the processor, further cause the computing device, prior to performing the first execution of the device-driven management workflow, to at least:

obtain the device-driven management workflow from a command queue associated with a management service; and

store the device-driven management workflow in the memory.

8. A computer-implemented method, comprising:

performing a first execution of a device-driven management workflow, wherein the device-driven management workflow comprises one or more branch sequences that are configured to be executed based at least in part on a state of a computing device and wherein the first execution of the device-driven management workflow executes at least a first branch sequence of the one or more branch sequences;

evaluating the computing device to determine a current state of the computing device;

comparing the current state of the computing device to an expected state of the computing device, wherein the expected state of the computing device is based at least in part on a result of the first execution of the device-driven management workflow by the computing device; and

in response to a determination that the current state of the computing device fails to match the expected state of the computing device, performing a second execution of the device-driven management workflow, wherein the second execution of the device-driven management workflow executes at least a second branch sequence of the one or more branch sequences based at least in part on the current state of the computing device.

9. The computer-implemented method of claim 8 , further comprising:

determining that the second execution of the device-driven management workflow failed; and

sending an error message to a management service, the error message comprising an indication that the second execution of the device-driven management workflow failed.

10. The computer-implemented method of claim 9 , wherein determining that the second execution of the device-driven management workflow failed, further comprises:

reevaluating the computing device to determine the current state of the computing device;

comparing the current state of the computing device to the expected state of the computing device; and

determining, based at least in part on a comparison of the current state of the computing device to the expected state of the computing device, that the second execution of the device-driven management workflow failed.

11. The computer-implemented method of claim 8 , further comprising:

determining that the current state of the computing device fails to match the expected state of the computing device further causes the computing device to at least:

identifying a current version of a resource installed on the computing device;

comparing the current version of the resource to a version of the resource specified by the device-driven management workflow; and

determining that the current version of the resource is less than the version of the resource specified by the device-driven management workflow.

12. The computer-implemented method of claim 8 , wherein determining that the current state of the computing device fails to match the expected state of the computing device further comprises determining that the device-driven management workflow has failed to previously successfully execute to completion.

13. The computer-implemented method of claim 8 , further comprising:

monitoring execution of individual tasks of the device-driven management workflow; and

reporting the execution of the individual tasks of the device-driven management workflow to a management service.

14. The computer-implemented method of claim 8 , further comprising:

obtaining the device-driven management workflow from a command queue associated with a management service; and

storing the device-driven management workflow in a memory of the computing device.

15. A non-transitory, computer-readable medium comprising machine-readable instructions that, when executed by a processor of a computing device, cause the computing device to at least:

perform a first execution of a device-driven management workflow, wherein the device-driven management workflow comprises one or more branch sequences that are configured to be executed based at least in part on a state of the computing device and wherein the first execution of the device-driven management workflow executes at least a first branch sequence of the one or more branch sequences;

evaluate the computing device to determine a current state of the computing device;

compare the current state of the computing device to an expected state of the computing device, wherein the expected state of the computing device is based at least in part on a result of the first execution of the device-driven management workflow by the computing device; and

in response to a determination that the current state of the computing device fails to match the expected state of the computing device, perform a second execution of the device-driven management workflow, wherein the second execution of the device-driven management workflow executes at least a second branch sequence of the one or more branch sequences based at least in part on the current state of the computing device.

16. The non-transitory, computer-readable medium of claim 15 , wherein the machine-readable instructions, when executed by the processor, further cause the computing device to at least:

determine that the second execution of the device-driven management workflow failed; and

send an error message to a management service, the error message comprising an indication that the second execution of the device-driven management workflow failed.

17. The non-transitory, computer-readable medium of claim 16 , wherein the machine-readable instructions that, when executed by the processor, cause the computing device to at least determine that the second execution of the device-driven management workflow failed, further cause the computing device to at least:

reevaluate the computing device to determine the current state of the computing device;

compare the current state of the computing device to the expected state of the computing device; and

determine, based at least in part on a comparison of the current state of the computing device to the expected state of the computing device, that the second execution of the device-driven management workflow failed.

18. The non-transitory, computer-readable medium of claim 15 , wherein the machine-readable instructions that, when executed by the processor, cause the computing device to determine that the current state of the computing device fails to match the expected state of the computing device, further cause the computing device to at least:

identify a current version of a resource installed on the computing device;

compare the current version of the resource to a version of the resource specified by the device-driven management workflow; and

determine that the current version of the resource is less than the version of the resource specified by the device-driven management workflow.

19. The non-transitory, computer-readable medium of claim 15 , wherein the machine-readable instructions, when executed by the processor, further cause the computing device to at least:

monitor execution of individual tasks of the device-driven management workflow; and

report the execution of the individual tasks of the device-driven management workflow to a management service.

20. The non-transitory, computer-readable medium of claim 15 , wherein the machine-readable instructions, when executed by the processor, further cause the computing device, prior to performing the first execution of the device-driven management workflow, to at least:

obtain the device-driven management workflow from a command queue associated with a management service; and

store the device-driven management workflow in a memory of the computing device.