'Crawled, currently not indexed' in Search Console: fix the pages or just resubmit?

Plenty of threads split on this status in Search Console. One camp says it's crawl budget and you need faster servers. The other says keep hitting Request Indexing until it sticks. I don't think either explains most cases on a small or mid-size site. Google has already crawled these URLs, so the bottleneck is the decision to index, and that usually comes down to whether the page adds anything the index doesn't already have. Thin category pages, near-duplicate product variants and tag archives are the usual culprits. My advice is to export the list, group it by template, and look for what the pages have in common before touching anything. Resubmitting a page that's basically a copy of another one just burns your quota and changes nothing.

Grouping by template makes sense, but "crawled, currently not indexed" also shows up on healthy pages that are just new, since Google can take weeks to get around to them. Before you blame the template, check when those URLs were first discovered. Thin pages and new pages look identical in that report.

Agreed that new and thin pages look the same in that report, and the GSC export doesn't give you a discovery date. The cleanest way I know to split them is server logs. Take the first Googlebot request per URL and bucket by age, because a page Google hit three weeks ago and still hasn't indexed is a different problem from one it first saw yesterday. If you don't have logs, sitemap lastmod and your CMS publish dates get you most of the way, though they're less reliable. Once the URLs are bucketed by first crawl date, the template grouping Kai suggested gets much more useful.

Log-based bucketing is the right call. One thing worth knowing is that URL Inspection won't give you the first crawl date, but the "Last crawl" field on a single URL plus the Crawl Stats report will tell you whether Googlebot has touched a page recently. If a page is still getting crawled every few days but sits unindexed, that's usually a quality call. If it hasn't been fetched in weeks, you're more likely looking at a discovery or priority problem.

Agreed on the last-crawl split. The Crawl Stats report only covers the last 90 days, though, so a page that was first crawled two months ago can look like it was never fetched. Compare the "Last crawl" date in URL Inspection against that window before you read silence as a discovery problem.

If the page's last crawl is older than the window, I'd treat it as a discovery problem and look at the sitemap and internal links before touching the content. If it was crawled recently and still isn't indexed, that's when the content becomes the thing to look at.