Flexpa - Issue with API – Incident details

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.