We are experiencing notarization submissions that remain in the “In Progress” state for an extended period (over 24 hours), with no status transition and no submission log available.
This is occurring in an automated CI environment using the Notary REST API (non-interactive submission and polling). Re-submitting the same package only results in additional submissions also stuck in “In Progress”.
There does not appear to be any API mechanism to cancel, clear, or expire these submissions once they are created.
We have already opened an Apple Developer Support case regarding this issue (Case ID: 102818066745 & 102819008943), but have not yet received clarification on what is causing these long-running “In Progress” states.
This issue is impacting our production release pipeline, as we are unable to reliably complete notarization for signed packages within an expected timeframe.
Based on other reports in this forum (including thread 811968), this behavior appears similar to cases where notarization requests were delayed due to backend backlog or in-depth analysis.
We would appreciate clarification on the following:
- Is it expected behavior for notarization submissions to remain in “In Progress” for such a long period without logs?
- Is client-side timeout and re-submission the recommended handling for CI workflows?
- Are there known service-side conditions (e.g. analysis backlog) that could explain this behavior?
Any guidance from Apple DTS or others who have encountered this would be greatly appreciated.