Notary service never completes our team's submissions: "In Progress" for 3+ days, even a hello-world binary

A few details to save a round-trip, since the first question is usually the state of the oldest request.

Oldest stuck submission, 258583f0-2322-4048-a97c-f290c63d849c (Compliance Vine.zip, created 2026-10-02 17:45 UTC), checked 2026-10-05 21:02 UTC:

% xcrun notarytool info 258583f0-2322-4048-a97c-f290c63d849c <credentials>
Successfully received submission info
  createdDate: 2026-10-02T17:45:04.544Z
  id: 258583f0-2322-4048-a97c-f290c63d849c
  name: Compliance Vine.zip
  status: In Progress

% xcrun notarytool log 258583f0-2322-4048-a97c-f290c63d849c <credentials>
Submission log is not yet available or submissionId does not exist
  id: 258583f0-2322-4048-a97c-f290c63d849c

Points that I think distinguish this from the failed-upload case in thread 829204:

• The requests have not disappeared from notarytool history; they've stayed "In Progress" for 3+ days and info still resolves them.
• Submissions come from a GitHub Actions macOS runner via notarytool submit --wait. Small hello-world uploads from the same pipeline complete, and two of them were eventually Accepted (after hours, not minutes), so upload and credentials work.
• Three builds of the same app are now held: 258583f0… (10-02 17:45 UTC), a7d7b1b1… (10-02 19:41 UTC), 1274bb4c… (10-03 13:27 UTC). Per the notary Q&A I've stopped resubmitting; a new version will upload once and wait.
• The App ID co.joyofwine.compliancevine is registered under the team.

If this is the additional-analysis path for a new Developer ID team, understood, but after three days I'd be grateful if someone could check the internal state of 258583f0… to confirm it's progressing rather than wedged. Happy to file a Feedback report if that's the right vehicle; please let me know the component.

Filed as FB25073190 (Developer Tools & Resources; the area list has no Notarization entry, so it's under "Something else"). It carries the same submission IDs and references this thread and support case 102984780721.

You’ve almost certainly encountered my standard spiel about this, but I’ve included it below just for the record.

but after three days

My experience is that this is longer than usual for the additional analysis path, but certainly not something completely beyond the pale. If this hits the week mark, reply back here and let me know.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for additional analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays.

For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive.

Resolved, thank you Quinn. The hold cleared on its own roughly four days after the first submission. Our builds submitted on October 2nd were accepted late on October 5th (UTC), and this morning's release build was notarised in under ten minutes per architecture: 1ceafbca-0774-4476-8502-907aaf6079fe (arm64) accepted 2026-10-06 13:49 UTC, 753fcc15-86cb-4cf7-8f64-411c85a2c446 (x86_64) accepted 2026-10-06 13:58 UTC. So this was the additional-analysis path for a new Developer ID team, as you said, just at the long end of it. For anyone landing here later: nothing on our side was wrong, the App Store Connect advice does not apply to Developer ID, and resubmitting the same build does not help. Wait it out, and open a support case plus a Feedback report so there is a paper trail if it passes a week. Marking your answer as correct.