Fortinet Due Care Due Diligence (Fake promise)

Hi All Community member and expert.

Do want to request whether you guys encounter or experience issue as below:

Incident that when request change of FortiSASE POP, the Fortinet engineer change without validating the settings (Which require deletion of Geo Fencing), which have configuration dependencies causing our specific POP down including whole SAML service down in FortiSASE on production. (Ticket 11464065)

While providing feedback on same ticket (11464065), the related Fortinet Manager promise to improve the procedure on next time check to check on the Geo Fencing and Fortinet engineer had log a bug in ticket (11398499) that will check whether there is existing Geo Fencing if customer request POP changes before implement.

We trusted Fortinet on that at the moment regarding the fix and procedure improvement.

Due to we have different Business Unit, we have another FortiSASE need request to change POP, then same issue happen causing production impact, further reported in ticket (11427683)

Do Fortinet really fix thing? Or just talk in words while not really executing?

In the same time, notice some release note that have similar bug issue that mentioned fix in previous version but reoccur

Bug ID (956918) appear in 7.2.3 under Known Issue
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/92e43e7f-99e3-11ee-a142-fa163e15d75b/forticlient-ems-7.2.3-release-notes.pdf

Mentioned fix on 7.2.4 under Resolved Issue
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/5e63575c-d4c7-11ee-8c42-fa163e15d75b/forticlient-ems-7.2.4-release-notes.pdf

Same issue mentioned fix appear on 7.4.0 under Resolved Issuehttps://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/541a9bf6-1f75-11ef-8c42-fa163e15d75b/forticlient-ems-7.4.0-release-notes.pdf

Not sure whether any other customer have such issue with Fortinet, or we are the “unlucky” one.