There is currently an issue with the web messenger. We’re looking into it now.

16:51 UTC: This is now resolved.

There are issues affecting bots currently. We’re looking into this now. We’ll update here within 30 minutes or sooner.

UPDATE 20:31 UTC: We believe this has been resolved but we’re still working on it. We’ll post here again within 30 minutes or sooner.

UPDATE 20:40 UTC: We’ve resolved the problem and are now monitoring. This issue was affecting some Telegram, Messenger, Twilio & web bots. Bots would be unresponsive and ‘Adapter not found’ would show up in the logs.

UPDATE 21:18 UTC: This is now resolved. Sorry for the trouble today.

There is some disruption to service currently. Were investigating now and will update here again shortly.

UPDATE 16:07 UTC: We’re working on a database related problem that is causing some queries to fail. Users will notice slow UI response times, timeouts, and some bot related functions not working as expected, or working intermittently. We’ll update again here within 30 minutes or sooner. Thanks for your patience as we work to resolve this.

UPDATE 16:34 UTC: The UI and bot functions have largely stabilized, flow logs are currently disabled. We’ll update with further news in at most half an hour.

UPDATE 17:14 UTC: Everything is working normally again, except for flow logs which are still unavailable for the moment. We expect to make them available again in the next 2-3 hours. We’ll post again once this happens. Sorry for the disruption today.

UPDATE: Logs are available again and everything is back to normal. Sorry for the problems today.

When users are clicking buttons, they are currently seeing a ‘not recognised’ response. They are then asked to type their response, which will allow them to proceed. We’re fixing the issue urgently now.

UPDATE 10:30: The problem is resolved.

We’re currently investigating an issue with Slack bots. They may be inaccessible or unresponsive at the moment. We’ll update here again within 30 minutes or sooner.

UPDATE 11:35: We’ve identified the issue and are working on a fix now.

UPDATE 12:05: We’re still working on this issue and hope to have a fix in place soon. There will be another update in 30 minutes or sooner.

UPDATE 12:36: Please bear with us as we continue to work on this. We will keep you updated here. Sorry for the problems today.

UPDATE 12:47: We’ve deployed a fix and all Slack bots are responding once again. Still monitoring the situation.

UPDATE 13:00: The issue is resolved, sorry for the issues today.

This is a reminder that between 9am-10am GMT on Tuesday 20th December, we’ll be performing some maintenance that will take your bots offline for approximately 30 minutes.

The maintenance will affect access to bots, access to the UI, and all triggers will be paused for the duration of the maintenance window.

We’ll keep you updated here as the maintenance progresses.

UPDATE 08:56: We’ll be starting the maintenance in about 5 minutes as planned.

UPDATE 09:02: The maintenance has begun. We’ll update again here once the platform is back online.

UPDATE: We’re back online. Historic logs may take up to a further hour to appear. Thanks for your patience today.

We’re investigating possible issues with webhooks. We’ll update here as soon as we have more information. In the meantime, some webhooks may return 404 when they should trigger a flow.

UPDATE 09:48 UTC: We have identified the issue and are working on this now. We’ll update again here within 30 minutes or sooner.

UPDATE 10:10 UTC: We’re still working on this but will update you again within 30 minutes or sooner. Thanks for your patience.

UPDATE 10:40 UTC: This is still being worked on and we’ll update you further shortly.

UPDATE 11:06 UTC: We’ve applied a fix for the issue and webhooks should now be working again. We’re monitoring the situation still to make sure it’s fully resolved.

UPDATE 11:19 UTC: The issue is resolved, sorry for the trouble today.

It seems that flowxo.com is not reachable currently. We’re investigating now and will respond in the next 30 minutes or sooner.

UPDATE 13:06: We believe this is an issue at our hosting platform. We’ll update when we have more information (or within 30 minutes). Thanks for your patience.

UPDATE 13:10: This issue will affect bots on the platform to, which won’t be responsive currently.

UPDATE 13:24: Our hosting provider has acknowledged the problem and is currently investigating. We’ll update here when we have more news, 30 minutes at the latest.

UPDATE 13:52: Sorry for the disruption today, our hosting provider is continuing to investigate the cause. We’ll keep you updated.

UPDATE 13:59: Service has been restored, although we don’t yet have information about the cause or resolution. We’re monitoring the situation.

UPDATE 14:49: This incident is resolved, that platform is operational again. We’re every sorry for the problems today.

Our scheduled maintenance window is now beginning, and will last up to 30 minutes. During this window you may find that: - Bots don’t respond to requests. - Bots won’t be able to send messages. - The Flow XO UI is inaccessible. Although this could affect service for the full 30 minutes, we’ll try to keep disruption to a minimum. Thanks for your cooperation!

UPDATE 07:38 UTC: The maintenance is complete, thanks for your patience.

We’re aware that Telegram bots are currently not responding. Investigating now. We’ll update here within again 30 minutes or sooner.

UPDATE 13:54 UTC: We’re still looking into the issue, and will update here in the next 30 minutes or sooner. Currently, some Telegram bots are not responding.

UPDATE 13:56 UTC: This issue is affecting existing Telegram bots, new bots or bots where a new token is generated seem to be working normally. We believe this may be a Telegram webhooks problem, as we’re not receiving requests in from Telegram as expected. We’ll keep you updated.

UPDATE 14:00 UTC: Until Telegram resolve the issue, you can use /token with @BotFather to get a new token, and edit your bot in Flow XO and save the new token. This should enable it to respond again. We’re still waiting for confirmation of the problem.

UPDATE 14:24 UTC: We’re still waiting for confirmation from Telegram as to what the problem is or when it might be fixed. We’ll update again here in the next 30 minutes or sooner.

UPDATE 14:55 UTC: There’s still a problem receiving Telegram webhooks, which mean some bots are unresponsive.

UPDATE 15:19 UTC: There are still problems, but we believe this is some issue with Telegram. There is a workaround, that you might want to follow to get your bot up and running again. You can use /token with @BotFather to get a new token, and edit your bot in Flow XO and save the new token. This should enable it to respond again. We’ll update this issue when we have more information for you, currently we don’t have any response from Telegram.

UPDATE 17:02 UTC: Unfortunately we still don’t have any details of what the problem is or the scope from Telegram. What we do know is, it’s easy to fix simply by editing your bot in Flow XO, and saving it. This sets the webhook URL again and your bot will start working again.

UPDATE 23:27 UTC: The problem was resolved at approximately 20:00 UTC by us programmatically resetting webhooks on all of our customer’s bots. Telegram have confirmed they lost the webhook addresses on a number of bots. This is resolved.