The message "Your request failed because database is locked." appears and I cannot update an app

Article Number:040294

When you try to update the settings of an app or perform another action, you may encounter the error message "Your request failed because database is locked. Wait a while and try again."
If you receive this error message, wait for a while and try to perform the action again. You may also want to try performing the action during a period when the app is not being accessed by many users, such as during the night.

Related Information: Workaround for errors

If apps contain a large number of records, fields, and configured permissions, it might take longer to update the apps, which can result in errors occurring more frequently. This can cause errors to occur not only for the app you are using, but also for other apps.
To avoid encountering errors, consider taking the following actions.

  • Update the app settings when the app is not being accessed by many users.

  • Reduce the number of records in the app.
    If there are large number of records in your app, consider splitting the app.

  • Reduce the number of fields in the app.
    If you delete a field, all the data registered to the field is deleted. Before deleting fields, be sure to create a backup by exporting existing records to a file.
    Refer to Exporting data to a file

  • Reduce the number of options set for option fields (e.g., Drop-down fields) in the app.
    If you have placed fields with a large number of options on your app form, consider reducing the number of options in the fields.
    Related Information: Instead of using fields with options, you can create a new master app that manages values for options, and then retrieve the value with Lookup fields.
    Configuring a "Lookup" field

  • Reduce the number of configured permissions.
    Consider organizing permissions, or removing unnecessary permissions.

  • Reduce the number of users/departments/groups with configured permissions.
    If you have applied the same permissions to multiple users, consider using a group or a department instead.