What's New in Version 2025.1.24-eec68944

New Features and Enhancements

A new api.resume_engine_async() procedure has been added to resume an engine without waiting for it to be ready. This procedure is useful when you want to resume an engine in the background and continue executing other tasks.
Minor improvements to internal error logs for improved support.

The api.resume_engine() procedure now blocks until the engine is ready to accept transactions. Previously, the procedure returned immediately after the engine was resumed, which could result in errors if you attempted to use the engine before it was fully initialized. Use the new api.resume_engine_async() procedure if you want to resume an engine without waiting for it to be ready.

Python API users will see a change in behavior when calling the Model constructor. If the engine set in their configuration is suspended, the constructor will now block until the engine is resumed. Previously, the constructor would return immediately, and the engine would be resumed asynchronously. The old behavior will be restored in the upcoming 0.7.4 release of the Python API.

Fixed a bug that caused shared object references to be deleted when a data stream was deleted. This bug could cause unexpected behavior when multiple data streams were created from the same Snowflake table or view.