#Appsmith crashed after auto update.
1 messages · Page 1 of 1 (latest)
Hello! I'm AppyBot, your friendly Appsmith support assistant. I understand that
you were experiencing an issue related to MongoTemplate that resolved on its own
within an hour. Since you don't have the error messages handy, it's challenging
to diagnose precisely what occurred. However, if you encounter similar issues in
the future, here are some general troubleshooting steps you can follow: - Check
the Appsmith server logs for any errors or warnings. - Review your MongoDB
queries and ensure they're correctly formatted. - Ensure your MongoDB instance
is running and accessible by Appsmith. - Verify your MongoDB datasource
configuration in Appsmith. - If a recent change was made in your Appsmith
application or MongoDB schema, review those changes. If the issue repeats itself
or you can provide me with more details or error messages, I can assist you
further. Meanwhile, it's good to monitor your application and keep any logs or
error messages for reference in case the issue reoccurs. If you don't find my
response helpful, you can request to speak to a human agent
Updates : It happened again, but this time, the service went down after i opened an edit page. Looks similar to this issue : https://community.appsmith.com/solution/application-crash-editlaunch-after-updating-v171-v178
The user experienced a crash on an Appsmith app when trying to edit or launch it, which occurred after they upgraded their server from v1.7.1 to v1.7.8. They suspected that the cause was a new organizationId field added to almost every file after the update. The user tried importing the app from the repository again, but the error recurred, maki...
Logs
Since you've provided a link to an issue on the Appsmith community but I can't
access it due to our current setup, let's try another approach: - Can you
describe the behavior or error messages you witnessed when the service went down
after opening an edit page? - Additionally, if you could attach any relevant
logs directly here, it would greatly help in diagnosing the issue. Once I have
more information about the error behaviors or log messages, I will be able to
assist you better. If you can't share logs or details here for any reason, I
would suggest reaching out to the Appsmith community or support with the
specific details of your issue. If you don't find my response helpful, you can
request to speak to a human agent
Someone from our team will reach out to you on this thread. If you change your
mind, you can ask to speak to an AI agent at any time.
will wait