# Flagship January release notes π
## Flagship January release notes π
## **Flagship New Releases**
## βοΈFlag configuration:
### **One unified workflow to rule them all.**
To further provide the best user experience in Flagship and maintain consistency, we have improved, streamlined but most importantly unified the flag configuration workflow across all use cases.
Since we care about all users and know that some prefer to configure a flag with a JSON format and others prefer to fill in the name, type and value of their flags, we have created 2 configuration modes: standard and expert so that everyone can follow their preferred path.
**Want to know more about it?**
π Consult the [Flag configuration documentation for an AB Test](https://flagship.zendesk.com/hc/en-us/articles/360022108620--Configuring-an-A-B-Test)
π Consult the [Flag configuration documentation for a Personalization](https://flagship.zendesk.com/hc/en-us/articles/360009983439--Configuring-a-Personalization)
π Consult the [Flag configuration documentation for a Feature Toggle](https://flagship.zendesk.com/hc/en-us/articles/4402780410258--Configuring-a-Feature-Toggle-Flag)
π Consult the [Flag configuration documentation for a Progressive Rollout](https://flagship.zendesk.com/hc/en-us/articles/360021707439--Configuring-a-Progressive-rollout)
##
## β
Status Page and Speed Page release:
### **More trust and transparency**
Have you ever had any doubts that some of the problems might have come from Flagship?\
With the new Status page you can find out if there is an issue with Flagship by visiting [status.flagship.io](http://status.flagship.io/). There you will find all information about Flagship services and the product maintenance we are working on.\
Do you want to know more about the response time of the decision API? You can check out [speed.flagship.io](http://speed.flagship.io/). You will get an overview of the overall response time in different regions.
##
## πImprovement of the platform's performance:
### **Full speed ahead!**
You may have experienced some performance issues in early December on Flagship. Since providing the best performance to our users is one of our top priorities, we quickly identified the reason (too many database calls) and worked on a solution.
Not only were we able to solve this problem by implementing a new Redis cache management system, but we also improved the overall performance of the platform.
Here are the improvements we made:
* We made each API call 30% lighter.
* We made the communication with the database smoother,
* We lightened the impact on the CPUs
* And we implemented a Read Replica so that the queries made by our background processes (CRONs) do not increase the load on the production database.
## **Feature in the previous release that you may have missed**
##
## π
Scheduler:
### **Stop worrying that you forget to launch an experiment or a personalization.**
Stressed out about forgetting you have an experiment to launch or busy with urgent business and not being able to launch the personalization you spent so much time on? What impact would it have on your business if you forgot about it while other stakeholders thought it was done? How much time and money would you lose by moving on to another task in a hurry to belatedly activate an experience or personalization?
Wouldn't it be great if you could agree with all stakeholders, set a date, and stop thinking about it to focus on other things?\
Flagship scheduler not only allows you to plan your experience or feature launch but also to be in sync with all your stakeholders and avoid any missteps of a GTM launch. Don't waste time or worry anymore about forgetting to toggle on a use case.
Try it now π
**Want to know more about it?**
π Consult the [Scheduler documentation](https://abtasty.zendesk.com/knowledge/articles/4404963619730/en-us?brand_id=360003208793)
---
# Agent Instructions: 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:
```
GET https://docs.abtasty.com/flagship-deprecated/release-notes/flagship-january-release-notes.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.