When I manually (I am not using an API call, so not a REST API quota) use https://web.archive.org/save I am sometimes/randomly/arbitrarily getting a red text "Job Failed." but it is a indescript silent error.
Is there a manual "user limit" known, where usually there are "API limits" known, but asking as a user/for users first now? Specifically, are HTML vs Screenshots "rate limited" by any publicly written rule?
I do not want to bother the archive.org team if somebody knows (or I will answer after asking by email).
Normally their errors show in the terminal-style log. The error is sometimes it does not show the normal loading screen/bar (then sometimes it does successfully save the HTML version but not the screenshot version, though not openly working apparently, I have to reload the https://web.archive.org/web/*/well https://web.archive.org/web/*/[YOUR_URL] to be exact version adding lots of time, and then it sometimes appears), seemingly when it feels like. Given it is going through the effort of giving me a command-line-looking loading screen why does it not just tell me what is happening like a good computer would even for the average user-superuser?
Any official information? Sometimes my archives save in 1 minute, then 45 seconds, sometimes 5, then 20, then another 30 seconds, then 90 minutes, then 30 minutes, then 25, then 110, then 50, then 20 (you get the idea?), then back and forth, then "Job Failed" then "Success", basically based on my ability to press again with my hand, which is not much advanced work. I have a 70% success rate by just pressing again and being patient.
I specified I am logged-in (real photo and real name, https://archive.org/details/@0037 is me), to avoid answers about "cloud protection" and "Denial-of-Service" n'"Suspicious" or "Hacking" errors, there are not any other devices at the same time making archives, I never use a VPN to obscure my location, there is not any automation/scripts, there is just me patiently pressing "Save Page" (for example, recently with all my Stackexchange questions, every edit, every mod, every comment, every q&a, every revision) one-by-one, which may be ~20 archives-per-activity a day (well 50 when heated discussion, is that what effected the next day?) for an average basic question.
I tried to load https://archive-it.org, archive.org's premier enterprise-grade logging service for institutions and organizations but am appalled that I can not duly pay to address whatever strain is apparent. I can not imagine an organization (saving zillions a second for legal backup) having to ask why even one archive does not save. The user service help/FAQ has zero information about user errors.
Does archive.org require you to personally email to find why, is it personal, are the errors personal? Is there any public information explaining their user rule set? In terms of this tool being by a tax-deductable non-profit which is nearly a public utility service, my preference is to ask publicly.