Everything is working normally again. Email notifications and alerts have been sending normally since 13:44 CEST, and the app, workflows and AI steps have worked normally since 09:43 CEST.

Between about 08:00 and 09:43 CEST, parts of the app returned errors, AI steps failed, and some scheduled workflows and API calls did not run. Between 08:00 and 13:44 CEST, some email notifications and alerts were not sent, and others arrived late.

If you rely on email alerts for failed runs, please check your run history for this morning and re-run any workflows that failed or did not run. We'll share a short write-up within 2 working days.

Update: The app, workflows and AI steps have been working normally since 09:43 CEST.

Still affected: email notifications and alerts are not being sent yet. We're working on restoring them and will post an update as soon as they're back.

Lleverage is mostly working again, but some services are still recovering.

What works: You can log in and use the app as normal, and workflows are running again.

What's still affected: Notifications are not being sent yet, so you may not receive alerts or emails about workflow runs for now. They will resume once the service is fully restored.

Google Cloud is still stabilising some of its databases, so you may occasionally see a slow response or a brief error. If so, please try again. We'll post another update once everything is fully restored.

Update: We’ve confirmed this is a wider issue caused by a database outage at Google Cloud, one of our infrastructure providers. As a result, parts of Lleverage are still unavailable or not working reliably. We’re working with Google to restore full service as quickly as possible, and we’ll post another update here as soon as we know more.

Since around 08:00 CEST, some requests to the Lleverage app are returning errors, and workflow steps that use AI models are failing or timing out. Our team has identified the affected service and is working on a fix. We'll post an update here as soon as we know more.