WaiterError: Run Command Waiter not able to access command ID right after send_command is invoked.

Describe the bug

Waiter unable to access SSM Run Command ID right after send_command is invoked. As a workaround, able to run without issues if sleep timer of 0.5-1 second is added or a looping in case of waiter error in try-except.

Steps to reproduce

response = client.send_command(Targets=[{"Key": "string", "Values": ["string"]}],
DocumentName="string", DocumentVersion="string")
commandID = response["Command"]["CommandId"]
waiter = client.get_waiter('command_executed')
waiter.wait(
    CommandId=commandID ,
    InstanceId='string',
    PluginName='string',
    WaiterConfig={
        'Delay': 123,
        'MaxAttempts': 123
    }
)

Expected behavior Use command ID to poll/wait until command is executed.

Debug logs {“errorMessage” : “CommandExecuted Failed” “errorType” : “WaiterError”}

[stobrien89]

Hi all,

Thanks again for the request. We are now submitting requests for paginators and waiters upstream so that all AWS SDKs benefit from a consistent implementation. I will pass on the request for this waiter state to the service team. We will also update the guidance in the contributing guide to better reflect this policy. I’ve added an issue to track this here:

aws/aws-sdk#86

Thanks again for bringing it to our attention!

[ayalganem55]

Facing the same issue when calling the waiter right after invoking the command: botocore.exceptions.WaiterError: Waiter CommandExecuted failed: An error occurred (InvocationDoesNotExist): adding sleep one sec solving the issue