AutoML workflows will no longer run with job compute
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-06-2024 12:16 PM
We have a few workflows that have been running fine with job compute (runtime 14x). They started failing on 6/3 with the following error: The cluster [xxx] is not an all-purpose cluster. existing_cluster_id only supports all-purpose cluster IDs. I was able to switch one to a single-user all-purpose compute but cannot select that same all-purpose compute from the other workflow that is failing. It's run as account is the same user as the compute. Any idea what changed on 6/3 to break these AutoML jobs or how to fix? Tried setting the job compute to use the latest LTS version of the ML runtime.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-15-2024 09:48 AM
Hi @c3,
We can see this Automl issue got fixed, can you check whether you are getting the same issue?

