Notarization stuck In Progress for 2+ days

Update: I tested with a minimal 7KB test.zip (simple signed app) using the same keychain profile. It also stuck in "In Progress" immediately, confirming the issue is account/team level, not related to the package content. Submission ID for test: 015ade60-c2f8-4af7-b535-3ae7fd5c9ffd

Update: Two separate teams affected, detailed timeline below

Team 1 (DocuAgile):

• 03-11 to 03-17 03:30 UTC: All Accepted (100+ successful submissions)
• 03-17 09:06 UTC: Suddenly all Rejected (statusCode 7000, "Team is not yet configured for notarization")
• 03-17 12:32 UTC: Brief recovery, 2 Accepted
• 03-17 13:08 UTC: Back to Rejected
• 03-18 13:51 UTC: Recovery again, 2 Accepted
• 03-19 02:30 UTC onwards: All stuck In Progress, logs return "not yet available"
• Tested with a 7KB minimal test.zip — also stuck: 015ade60-c2f8-4af7-b535-3ae7fd5c9ffd

Team 2 (separate account):

• 03-11 to 03-17 03:30 UTC: All Accepted (100+ successful submissions)
• 03-17 09:06 UTC: All stuck In Progress, never recovered
• Agreement was not signed — signed it today, still no recovery
• All submission logs return "not yet available"
• Earliest stuck submission: 789d40c4-ff83-469f-9b9b-2ac93183125e (2026-03-17 09:06 UTC)
• Latest stuck submission: ef7f8dbb-a7db-44c8-910c-532761b2a528 (2026-03-19 11:53 UTC)

Both teams have valid Developer ID Application certificates (expiry 2031). Issue is not related to package content or size — minimal test package also affected. Could you please check the backend queue status for both teams?

Update: We received an App Review rejection on 2026-03-17 06:02 UTC for Guideline 4.1(a) (Copycats - references to OpenClaw). The notarization queue started failing at

2026-03-17 09:06 UTC, exactly 3 hours after the rejection. Could this App Review rejection have triggered a backend review of our account affecting notarization?