Wow, I didn't know about these errors! Is this why I can't write a field or document to the MongoDB collection? I definitely didn't write my script to add array types into the schema, at all.
Initially, the database schema was created via the Parse Dashboard. I populated that with a collection of approx 600 thousand documents (each containing about approx 12 fields of scalar data-types), by way of a script written in Java and seeded into said collection via Android Studio.
I knew that MongoDB leverages a dynamic schema, so at a later date, when the collection needed additional information (information that would inevitably alter by adding/expanding the schema) I wrote a script in Android Studio --adding to the schema and seeding the database on the fly with my new data i.e.:
...I think that's how i did it. I don't have the code in front of me at the moment.
So, by this point, those same ~600 thousand documents had a new schema which allowed for approx 32 fields of scalar data-types. With Android Studio I ran a script that seeded the new fields, completing a few thousand documents within that collection. My cloud storage space got extremely low (about 1gb available, making me fear the 503 I've experienced before with a full disk) so I suspended the script -which is something I had done several times before in the past- to address the storage issue. Later on, when I went to resume by running the script again I got the 503 Service Unavailable.
I'm at a loss... On how the errors occurred.
Another thought... Despite this error, it still doesn't explain why I'm getting a 503 when I attempt to view the DB via Parse Dashboard... or does it?