The Logs page helps you see what you’ve done, and is particularly useful in monitoring duzzits that are running autonomously or are externally invoked (e.g. scheduled duzzits and duzzits that are called as web services or widgets).
In addition to seeing a summary of how many duzzits you’ve run, duzzit widgets that have been run, emails that have been sent, and SMS messages that have been sent, you also can see a list of results for each of these runs. When you go to the logs page, the listing you see by default is for duzzit runs. In the graphic above, you can see that the duzzit named “Salesforce Lookup Tasks” has been run twice. In the first of these runs, there were errors. You can click on the details link to see more information. In this case, clicking on details for the run with errors shows this:
So, we see that this duzzit failed, as it requires that a connection to Salesforce be configured in order to run successfully.
If you encounter an error or an unexpected result when running a duzzit, the first thing to do is to check the logs page. In most cases, errors in duzzit runs will have been caused by configurations issues (such as not having setup a required connection), or by limit issues (such attempting to run duzzits or send SMS messages more frequently than is permitted by your account level).
