Message for current status of an instance in the
BatchCreateInstances operation. For example, lets say a
BatchCreateInstances workflow has 4 instances, Instance1 through
Instance4. Lets also assume that 2 instances succeeded but the third
failed to create and the 4th was never picked up for creation
because of failure of the previous one. Then, resulting states would
look something like:
Instance1 = ROLLED_BACK
Instance2 = ROLLED_BACK
Instance3 = FAILED
Instance4 = FAILED
However, while the operation is running, the instance might be in
other states including PENDING_CREATE, ACTIVE, DELETING and
CREATING. The states / do not get further updated once the operation
is done.
Attributes
Name
Description
state
google.cloud.alloydb_v1alpha.types.BatchCreateInstanceStatus.State
The current state of an instance involved in the batch
create operation. Once the operation is complete, the final
state of the instances in the LRO can be one of:
1. ACTIVE, indicating that instances were created
successfully
2. FAILED, indicating that a particular instance failed
creation
3. ROLLED_BACK indicating that although the instance was
created successfully, it had to be rolled back and
deleted due to failure in other steps of the workflow.
error_msg
str
DEPRECATED - Use the error field instead.
Error, if any error occurred and is available,
during instance creation.
error
google.rpc.status_pb2.Status
The RPC status of the instance creation
operation. This field will be present if an
error happened during the instance creation.
Classes
State
State(value)
State contains all valid instance states for the
BatchCreateInstances operation. This is mainly used for status
reporting through the LRO metadata.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Class BatchCreateInstanceStatus (0.4.8)\n\nVersion latestkeyboard_arrow_down\n\n- [0.4.8 (latest)](/python/docs/reference/alloydb/latest/google.cloud.alloydb_v1alpha.types.BatchCreateInstanceStatus)\n- [0.4.7](/python/docs/reference/alloydb/0.4.7/google.cloud.alloydb_v1alpha.types.BatchCreateInstanceStatus)\n- [0.3.16](/python/docs/reference/alloydb/0.3.16/google.cloud.alloydb_v1alpha.types.BatchCreateInstanceStatus)\n- [0.2.1](/python/docs/reference/alloydb/0.2.1/google.cloud.alloydb_v1alpha.types.BatchCreateInstanceStatus)\n- [0.1.1](/python/docs/reference/alloydb/0.1.1/google.cloud.alloydb_v1alpha.types.BatchCreateInstanceStatus) \n\n BatchCreateInstanceStatus(mapping=None, *, ignore_unknown_fields=False, **kwargs)\n\nMessage for current status of an instance in the\nBatchCreateInstances operation. For example, lets say a\nBatchCreateInstances workflow has 4 instances, Instance1 through\nInstance4. Lets also assume that 2 instances succeeded but the third\nfailed to create and the 4th was never picked up for creation\nbecause of failure of the previous one. Then, resulting states would\nlook something like:\n\n1. Instance1 = ROLLED_BACK\n2. Instance2 = ROLLED_BACK\n3. Instance3 = FAILED\n4. Instance4 = FAILED\n\nHowever, while the operation is running, the instance might be in\nother states including PENDING_CREATE, ACTIVE, DELETING and\nCREATING. The states / do not get further updated once the operation\nis done.\n\nClasses\n-------\n\n### State\n\n State(value)\n\nState contains all valid instance states for the\nBatchCreateInstances operation. This is mainly used for status\nreporting through the LRO metadata."]]