Logs

What Are Logs?

Logs give you an audit of all the workflows you’ve processed. If you want to check whether or not a workflow is working the way you intend, this is the place to go. Logs are intended to be used for troubleshooting, or confirming the flows you have are working as expected.

A ‘workflow’ is a collective term for the series of flows that execute against a single event. A log will therefore relate to a single occurrence of an event you have defined.

Click on any log to open it up, and you should see something like this (bearing in mind the flows shown below will be different to the ones you’re using):

A log of an event, showing three successful flows.

Using Logs

The list of logs you can see display in chronological order.

When opening a log, you’ll see the event that happened at the top. You’ll get a bunch of information, such as how long it took to run, finish, and what type of event it is. If you want to access the event directly, click

A log will show the events in the order you saved them when you added them in the Events section. Click on a flow to see exactly what happened, and when. In some cases, you’ll see another dropdown which will show more detailed information. The log will display each Action that happened, and what it did for each one in chronological order from top to bottom.

If you want to get a visualisation of the log, use the to see the flow. You can hover over any action, and it will show you the logs that correlate to it, which makes it much easier to understand what’s happening. If you want to make changes to this event, use the to go to the Builder.

Erroring Logs

It’s important to know when things go wrong, and be able to react to them quickly. If an event errors, you can see it in logs. To see a list of errored logs, you can check the ‘errored' section below.

View errored logs by switching to ‘Errored’ under the search.

If you select a log that has errored, you’ll see the flow that it has errored on. The action that is red is the specific action that has errored:

Any text in red will explain why the action has errored.

Whilst we’ve tried to make errors clear and easy to understand, they can still be confusing. If you ever see an error and don’t know how to fix it, please reach out so we can help.

Clicking on the will visualise the flow, so you can see where it errored. It can help to work out what has gone wrong if you can see the bigger picture leading to the error!

Tips and Tricks for Logs

If you see a in the top left of the builder when looking at a flow, hover over it to see how many times the log has errored. It’s a great trick for seeing problems at a glance!
You might see the same timestamp for numerous Actions. Don’t worry, Gnatta processes actions milliseconds apart, they aren’t processing at exactly the same time!
Logs will only be saved for one hour, so you’re not able to view any logs that are older than this.
Use the search bar! You’ll have a lot of logs and it can be difficult to find what you’re looking for.