[Python] How to fix the GSException: "Container not found" even when the container exists?

I’m working with GridDB Cloud and using the griddb_python client to write and read data from a container called "device_metrics" which I created successfully using:

store.put_container("device_metrics", [
("timestamp", griddb.Type.TIMESTAMP),
("device_id", griddb.Type.STRING),
("temperature", griddb.Type.FLOAT)
], griddb.ContainerType.TIME_SERIES, True)



After running this, I confirmed via GridDB Web UI that the container exists.

However, when I try to access it later in a different part of the script like this:

container = store.get_container("device_metrics")


I intermittently get the following error:

griddb.gsexception.GSException: [PARTIAL_EXECUTION(0x0303)] Container not found. (Container name='device_metrics')



What I’ve checked:

• Double-checked the spelling of the container name (case-sensitive).
• Tried using store.get_container("device_metrics") immediately after creation — sometimes it works, sometimes not.
• Used store.get_container_info() — which also fails occasionally with the same error.
• This issue appears more often when running scripts from multiple threads.

Question

• What causes GSException: Container not found in GridDB when the container definitely exists? Is there a delay in container propagation in GridDB Cloud after creation?

Continue reading...