Flexpa - Notice history

This incident has been resolved.
This did not affect any customer implementations or integrations with Flexpa Link.

Why did it happen?
We promoted an environment change in MyFlexpa's dev mode, and had to complete unexpected manual steps to redeploy the MyFlexpa application.

How to prevent in future?
Improve our internal change process for updating MyFlexpa's environment configuration by removing unnecessary manual steps.

This incident has been resolved.

Why did it happen?
Flexpa released a fix to accommodate a scenario where some payer authentication flows were incompatible with Safari. However the fix, which uses cookies to handle communication between Flexpa Link and Flexpa API, introduced a bug which was undetectable in the development environment because the development environment shares the same domain across services.

How do we prevent it in the future?

• Broaden test suite across browsers. Safari, Chrome, Firefox etc.
• Test across multiple domains in the development environment

We implemented a fix and are currently monitoring the result.

We are continuing to work on a fix for this incident.

This incident has been resolved.

Why did it happen?
The new parameter in Flexpa Link was checked if it was defined, and so the word "undefined" was being serialized into the Flexpa Link application state, and the application was crashing on this unexpected value.

How do we prevent it in the future?

• Include Flexpa Link (package) in our CICD test suites.
• Implement a UX Monitoring alarm on MyFlexpa to test that Link is loading successful

We have resolved the issue with our API.

The database cache our apps connect to was destroyed in the course of a configuration change today.

This prevented a service from being online.

That service being offline meant that every new Patient Access Token transitioned to an error state. An error state was shown visibly to patients / our customers and Links do not occur successfully.

This impacted all customers (excepting those opted out from our data cache) because every new Patient Access Token requires this step to successfully complete.

We completed resolution of this event once we had all applications pointed at the new data cache.

Flexpa takes downtime such as this event seriously. We have completed a post-mortem procedure and will be introducing changes to our process to prevent this issue from re-occurring.