# Ansible GCE Instance Start and Stop -   LibcloudError  - job did not complete in 180 seconds

**URL:** <https://forum.ansible.com/t/ansible-gce-instance-start-and-stop-libclouderror-job-did-not-complete-in-180-seconds/29568>\
**Category:** Ansible Project\
**Tags:** gcp\
**Created:** [January 30, 2019, 3:21am UTC](https://forum.ansible.com/t/ansible-gce-instance-start-and-stop-libclouderror-job-did-not-complete-in-180-seconds/29568 "2019-01-30T03:21:27Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![bo.mannarino](https://avatars.discourse-cdn.com/v4/letter/b/ed8c4c/32.png) [@bo.mannarino](https://forum.ansible.com/u/bo.mannarino)\
**Post date:** [January 30, 2019, 3:21am UTC](https://forum.ansible.com/t/ansible-gce-instance-start-and-stop-libclouderror-job-did-not-complete-in-180-seconds/29568/1 "2019-01-30T03:21:27Z")

</div>

We have (GCP) GCE instance start and instance stop playbooks. Tonight’s execution was the stop of 8 GCE instances at once. The main script is kicked off and the playbooks run in background.

We are seeing this error -

### An exception occurred during task execution. To see the full traceback, use -vvv. The error was: libcloud.common.types.LibcloudError: \<LibcloudError in None ‘Job did not complete in 180 seconds’\>

We assume this may be related to needing some tuning, but, we are not exactly sure where or what. Can anyone help here ?

THanks BAM