Three notarization submissions stuck “In Progress” 17+ hours — first submissions for a newly issued Developer ID team

All notarization submissions from our team are stuck at “In Progress”; none has reached a terminal state (neither Accepted nor Invalid). Environment • Team ID: F2Q623H7F9 • Developer ID Application certificate issued 2026-07-25 18:35 UTC. These are this team's first-ever notarization submissions — there is no prior successful notarization to compare with. • Auth: App Store Connect API key (.p8 + key ID + issuer ID), not an Apple ID password. • Submitted with • Payload: xcrun notarytool submit from GitHub-hosted macos-14 runners, not a local Mac, so a client-side upload crash is not a factor. ditto -c -k --keepParent zip of Mel.app, ~17 MB — a native Rust/egui desktop app. Not Electron; no accessibility APIs. Stuck submissions — all three still “In Progress”, confirmed via both xcrun notarytool info and independently via the Notary REST API ( GET /notary/v2/submissions/{id} ): 1. 8ad4dde0-06f1-43b5-acf4-2847b4cce10e — created 2026-07-25 21:39:24 UTC (oldest; 17+ hours elapsed) 2. 9d60e50e-474c-41f6-920d-1b4a1e1f57b4 — created 2026-07-26 10:24:32 UTC 3. cea068bb-6ffa-4a18-ba49-0dec625071ca — created 2026-07-26 11:25:48 UTC Every upload was accepted (“Successfully uploaded file”). None was rejected. xcrun notarytool log <uuid> returns “Submission log is not yet available”, which we understand is expected for a non-terminalsubmission. Signing verified locally before each submission codesign --force --deep --timestamp --options runtime --entitlements <path>/mel.entitlements --sign "Developer ID Application: … (F2Q623H7F9)" Mel.app codesign --verify --deep --strict --verbose=2 Mel.app → “Mel.app: valid on disk” and “Mel.app: satisfies its Designated Requirement”. Hardened runtime enabled; secure timestamp present. Service status — the Developer ID Notary Service has shown “Operational” on developer.apple.com/systemstatus for the entire window covering all three submissions. What we have deliberately not done — we have stopped resubmitting. We understand that re-uploading the same build only adds backlog for the service to grind through once the state clears, so we are holding at three submissions and polling instead of retrying. Request — we are not asking for a rejection reason; nothing has been rejected. We are reporting the UUIDs and creation dates as the guidance asks, so these can be distinguished from orphaned submissions that will never reach a terminal state. Question: Are a new team's first submissions subject to an extended review period, and if so what completion time should we expect for 8ad4dde0-06f1-43b5-acf4-2847b4cce10e?