Should it be considered wrong to save the state information of an application in a database?

Storing information about the status of an application in a database is not wrong, and is often a necessary and correct approach. It allows:

• To track the current status of the application (e.g., "new", "in progress", "completed").
• To ensure data consistency and the ability to recover the state after failures.
• To support business logic and reporting.

It is only important to properly design the data model and ensure the relevance of the status to avoid discrepancies between the actual state and the stored one. For example, if the application status depends on external processes, mechanisms for synchronization and updating should be considered.