Base Job Configuration section (UI) of custom work pool disappears when adding a block reference

[bjorhn]

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 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.

MRE: https://gist.github.com/bjorhn/2037a580f57b78813a7caf4419e60cfe

Version info (prefect version output)

Version:             3.0.8
API version:         0.8.4
Python version:      3.11.10
Git commit:          0894bad4
Built:               Thu, Oct 10, 2024 10:17 AM
OS/Arch:             linux/x86_64
Profile:             local
Server type:         cloud
Pydantic version:    2.9.2
Integrations:
  prefect-azure:     0.4.0
  prefect-dbt:       0.6.1
  prefect-shell:     0.3.0
  prefect-snowflake: 0.28.0

Additional context

@zzstoatzz confirmed in slack that this issue happens in both Prefect Cloud and the open-source server.