Missing Autosave Feature in Directus: Why Can't I Save My Services Automatically?

As you know, we leverage Directus as the foundation for constructing our Service Map, where each service, once published and/or translated, becomes accessible on our program websites.

There are a few reasons why we’re unable to have the autosave feature in our Directus:  

1. Data Integrity Concerns: Autosave can potentially lead to data inconsistencies if multiple users are editing the same item simultaneously. Directus might prioritize data integrity over convenience.  
2. Performance Considerations: Implementing autosave can impact system performance, especially with a large number of users or complex data structures. Directus might have opted for a more streamlined approach to focus on core functionalities.  
3. User Control Preference: Some users might prefer manual saving to have full control over when changes are saved, preventing accidental overwrites or unintended modifications.  
4. Development Priorities: Autosave is not a top priority for Directus, potentially due to other features taking precedence, therefore blocking our internal Signpost Development Team to continue with this request.  

Our investigation into Directus' capabilities revealed limitations in its current feature set. Notably, the platform lacks an essential autosave function. Directus' flexible structure, allowing optional fields and draft saving, while convenient, doesn't compensate for the absence of this critical feature. 

Workarounds 

While Directus does not have a built-in autosave feature, you can implement these workarounds:  

• Frequent Manual Saving: Develop a habit of saving your work regularly, and specifically in Draft mode when creating and editing a new Service.  

• User Feedback: Provide feedback to the Directus community. 

To mitigate potential data loss due to Directus' lack of autosave, we strongly recommend frequent manual saving. This proactive approach is crucial given the platform's current limitations.