aws glue import-catalog-to-glue still pending after 3 weeks

Question

So, a few weeks ago, we got a message from AWS saying (I'm paraphrasing), "Things from Athena are being deprecated, so you need to do these things to migrate them to AWS Glue."

In our case the affected resource is a data catalog, rather than API calls, and the suggested function to use was:

aws glue import-catalog-to-glue --region {region} --catalog-id {catalogId}

Well, I went into the AWS CLI and ran that with the correct region and catalog ID, and in the AWS Health Dashboard, it said it was pending. I really thought no more of it, and went on with other work matters.

It's three weeks later, and it's still pending. (And we just got another notice about the same issue, from AWS.)

I looked through the documentation on that function, and got no additional insight from it. If this were an EC2 instance, I would think that stopping the database would let the command run, and then I could just restart the database.

But there doesn't appear to be anything in the UI for the data catalog that is a "Stop" to let this command finish (or at least move from a "Pending" status to an "In Progress" status, or whatever.)

What am I missing?