Custom connectors (published by an admin) do not show in the Apps directory in business workspace so members cannot find and use them

I have a pre-existing custom connector (MCP server with search and fetch) that is now an “app” that had been published to the business workspace and working consistently for months. After the migration to “Apps” no workspace users can see or access it except for the admin that published it to the workspace who sees it under enabled. Even if I delete and recreate it, re publish/enable etc only that original admin can ever see and use it (it works)i I suspect there are some wires crossed with the Apps permission. It should show in the directory for other workspace users after publishing I would assume. Another admin can see it in the directory, but it is not enabled, and if they try to enable it there is an error “only an admin can enable” (despite them being an admin) and my admin account having already published it and consented to the form).