> For the complete documentation index, see [llms.txt](https://docs.deepwork.studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deepwork.studio/teams-departments/operations/roles/software-maintenance/workflow.md). # Workflow ## Monitoring Metrics and Server Capacity Periodically, check PROD Monitoring metrics for time response spikes and 500 errors. If 500 errors occur, examine logs to determine the cause and implement a fix. In the case of time spikes, ensure the current server plan is sufficient to handle the workload, and consider upgrading if necessary. ## Addressing Reported Bugs When bugs are reported, attempt to reproduce the issue using the provided scenario. If reproducible, review the related front-end code to understand the logic and identify the root cause. Once determined, fix the issue and implement updates to prevent future occurrences (e.g., refactor code, add tests for specific use cases). ## Database Maintenance and Consistency Occasionally, update minor parts of the database where the user interface does not allow changes (e.g., reverting an action). It is vital to maintain consistency and keep the PROD environment clean. ## Tracking Proposals and Requests Monitor all proposals and requests, including those you have created and those that are good to have/fix/update, by creating tickets in the TODO list on the Notion table: [https://www.notion.so/deepworkstudio/7cb0046a3cb1419d82b464de03b07740?v=4](https://www.notion.so/deepworkstudio/7cb0046a3cb1419d82b464de03b07740?v=4c33cd9fa17d42f4884139a2e61ed8c0\&pvs=4) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.deepwork.studio/teams-departments/operations/roles/software-maintenance/workflow.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.