Since around 6am this morning, all IFTTT applets that are initiated via Apilio are failing, with a “Trigger failed” error message. This is happening with various different IFTTT applets, interfaced with different Apilio Logicblocks.
It looks like something has happened at the Apilio end.
Is this something that is specific to my account(s) or a general issue?
@pebneter – any ideas?
Everything started working again at 9:56. So things were out of action for nearly 4 hours, but I’m relieved that are are back!
Sorry for the service interruption!
I see in the logs that the app was not responding for a while for some requests.
The reason is not clear yet. There was a database upgrade by the service provider yesterday and we made a small deployment, but both should not have such in impact.
Operation seems to be back to normal by now. We will continue to observe and try to find the root cause.
Seems like this issue has recurred. On one logic block - First on Feb 2nd at 16.17 and then again today (Feb 4th) at 16.21 and again at 17.06 the trigger failed with IFTTT error message ‘The service took too long to respond’.
A separate logic block had the exact same problem Feb 2nd at 16.15 and then today (Feb 4th) at 16.19 and again at 17.04.
Prior to this, and on 3rd Feb, both functioned as intended.
Anyone else experiencing this?
These two notifications just arrived. Maybe they shed some light?
Hi @Antyronnen ,
thanks for your report.
It seems that Apilio is responding to slow to IFTTT, leading to timeouts and the error you see.
I did temporarily increase the resources to see if this reduces the amount of errors. Please update here if you run into more issues in the coming days.
Hi pebneter, thanks for the update. Tonight one apilio ‘call’ to IFTTT went through OK at 16.21 and another two minutes later threw up the same error message. I’ll monitor and let you know what happens.
What’s your time zone?
Sorry, I should have said. GMT
Been monitoring for the last two days. All now working as before. Many thanks for sorting this.

