If you'd like to view a history of your Applet runs or check the activity for a specific Applet, you can do so through the activity feed. This is a helpful way to see when an Applet last ran, whether it was successful, and if any errors occurred.
This article explains how to view your Applet’s activity, understand what different messages mean, and troubleshoot issues.
Accessing the activity feed
To see activity across all Applets, go to ifttt.com/activity. You can also press your profile icon and select Activity. This page shows a feed of recent Applet runs along with any new service connections.
Each Applet also has its own individual activity feed. To view the activity for a specific Applet:
-
Go to ifttt.com/my_applets or open the IFTTT app and tap My Applets.
-
Press the Applet you want to review.
-
Select View activity.
You’ll see a list of events showing the last time the Applet ran, what triggered it, and whether it completed successfully. If something went wrong, the activity feed will usually indicate what happened and whether the issue came from the Trigger, Query, or Action.
Viewing the activity feed
When viewing the activity feed, you’ll see a list of Applet runs in chronological order, with the most recent at the top. Each entry shows the status of the Applet’s Trigger, Query, and Action, along with timestamps for when each step occurred.
To the right of each step, you’ll see a dropdown icon. Pressing this icon expands the entry to show more details about that part of the Applet:
When expanded, you can review the specific Ingredients passed from the Trigger and any Queries, as well as the field values used in the Action. This can be especially helpful for troubleshooting issues or understanding exactly how your Applet ran.
Trigger type
At the top of each Applet’s activity feed, you’ll see a message indicating the type of Trigger it uses:
-
"Successful Trigger checks" means the Applet is using a polling Trigger.
-
"Listening for Trigger notifications" means the Applet is using a real-time Trigger.
Understanding whether an Applet uses polling or real-time Triggers can provide helpful context. It can give you a sense of how quickly the Applet should run after a Trigger event, and it can also be useful when troubleshooting issues.
You can learn more about the difference between polling and real-time Triggers here: What is the difference between polling Applets and realtime Applets.
Troubleshooting tips
If your Applet isn’t running as expected, here are some steps you can take to diagnose and resolve the issue.
Check the Activity Feed
Start by viewing the Applet’s activity feed. If something went wrong, you’ll see a message such as "Trigger failed," "Query failed," or "Action failed", depending on where the issue occurred. Press the dropdown arrow next to the relevant step to expand the details. An error message may be shown that explains what went wrong and which part of the Applet encountered the issue.
This can give you a clear idea of whether the problem lies with the service providing the Trigger, the data returned by the Query, or the service handling the Action.
Check the Ingredients used in the Applet
If a Trigger or Query doesn’t return the expected data, it could cause the Action to fail. You can expand the details for that portion of the Applet run in the activity feed to view exactly what data was passed in each Ingredient.
If you see “Action failed”, this can sometimes be due to missing or incorrectly formatted data coming from a Trigger or Query. For example, if your Action expects a URL but the Ingredient passed is empty or contains unexpected text, it may not complete successfully. Review your Applet’s settings to confirm the correct Ingredients are mapped to the appropriate fields.
Reconnect the Service
Reconnecting the service connected to the failed step can often resolve the issue.
If the problem occurred in the Trigger, go to the Trigger service’s page, select Settings, and then choose Reconnect.
Similarly, if the error happened during the Action, follow the same process on the Action service’s page.
Consider Polling Frequency
If your Applet uses a polling Trigger, IFTTT checks for updates at set intervals:
-
Every 5 minutes on IFTTT Pro and IFTTT Pro+
-
Once an hour on the Free plan
Sometimes these checks may fail due to issues like a service's API not responding in time. When that happens, you’ll see a failed trigger check in the activity feed.
If a Trigger event occurred during that failed check, the Applet will run at the next successful check. If no event occurred, the Successful Trigger checks heading will show that the next check succeeded with no new events found.
If a Trigger Event hadn't occurred around the time of the failed check then its best to think of these failed checks as IFTTT being temporarily unable to check if your Applet should run at that time, not that it missed a event it should have run for.
Contacting support
If you’re still having trouble after trying the above steps and you’re on an IFTTT Pro or IFTTT Pro+ plan, you can reach out to our support team for help. For guidance on how to contact support, please visit: How to contact support
Previous Section: Managing services on IFTTT | Next section: Staying connected