Checking, logging, and analyzing event triggers and data is paramount to bridging data and systems for M2M development and many application developments. During troubleshooting and analysis, Ubidots' Support team often hears, "How can I know if my event was triggered? I did not receive any messages."
Often, all the information needed can be found in the Ubidots event's logs. Located in the events' page, you can easily trace the regularity and reliability of your events.
For example, let's say we have an event configured to that if variable == 1, then a webhook will be triggered to maker.ifttt.com.
In the below two images, we can trace the multiple variable limits of 1 and its corresponding events in the webhook event's Log at 21:18:09 and 21:18:32.
Variable view:
Event log:
Still need help?: If you suspect an event should've triggered, but didn't, reach out to Ubidots support with screenshot evidence of the event's variable values tables pointing to the value that should have triggered an event and a second screenshot of the event log stating that no such trigger exists. This will greatly help Ubidots Customer Success and Development teams to verify the consistency of the module and isolate any possible anomalies in your situation.