You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating a work pool by running a custom worker for the first time, the work pool behaves as expected until you add a block reference to it. After saving the changes, the next time you look at the work pool, the section under "Base Job Configuration" will be empty:
I'm not sure if this happens with all types of blocks, I've tried it with AzureContainerInstanceCredentials and SnowflakeCredential.
The same thing happens if you create the work pool using the --base-job-template argument to prefect worker start, pointing at a template that contains a block_document_id reference.
I can confirm that the settings (including the block) do get saved correctly, since I can retrieve them with no issues when running deployments on my custom worker connected to the work pool.
Bug summary
When creating a work pool by running a custom worker for the first time, the work pool behaves as expected until you add a block reference to it. After saving the changes, the next time you look at the work pool, the section under "Base Job Configuration" will be empty:
I'm not sure if this happens with all types of blocks, I've tried it with AzureContainerInstanceCredentials and SnowflakeCredential.
The same thing happens if you create the work pool using the
--base-job-template
argument toprefect worker start
, pointing at a template that contains a block_document_id reference.I can confirm that the settings (including the block) do get saved correctly, since I can retrieve them with no issues when running deployments on my custom worker connected to the work pool.
MRE: https://gist.github.com/bjorhn/2037a580f57b78813a7caf4419e60cfe
Version info (
prefect version
output)Additional context
@zzstoatzz confirmed in slack that this issue happens in both Prefect Cloud and the open-source server.
The text was updated successfully, but these errors were encountered: