Intermittent NuGet pushes usually aren’t a packaging bug but an upload/validation/visibility issue in the feed. Things to check quickly:

• Capture the server response: run the push with verbose logging (e.g. nuget/dotnet nuget push with -Verbosity detailed or --verbosity detailed) and save the HTTP status and body. That tells you if the server accepted the file or returned an error that your script is swallowing.
• Watch for conflict/duplicate/version collisions: a 409/409 Conflict or similar means the version already exists (or partial metadata exists) and will make the package non-editable until resolved.
• Processing / indexing delay: many feeds (including GitHub Packages / NuGet hosts) process uploads asynchronously — the package file may be present on storage but the package is still being validated/indexed and won’t be editable/visible until processing completes. Add a short retry/backoff and re-check the package metadata endpoint instead of only checking storage.
• Auth / token scope and transient auth errors: confirm the push token has the correct scope and isn’t intermittently rejected (look for 401/403 responses).
• Feed-side validation failures: malformed nuspec metadata, missing required fields, or invalid characters/length in ID/version can cause silent validation failures. Validate the package locally and compare nuspec metadata against feed limits.
• Check feed/registry logs & status: use package feed UI/audit logs (if available) and the provider’s status page to rule out service incidents or replication delays.

Suggested immediate fixes: enable detailed logging in the push command and capture responses, implement retries with exponential backoff, and add a post-push validation step that queries the feed’s package metadata endpoint (so you fail loudly if processing didn’t complete). These steps will show whether this is client-side, transient network/service behavior, or a feed validation problem.