When an integration is not behaving as expected, Cinode gives you the full execution history and logs of every deployed instance, so you can see exactly when it ran and what happened. This article shows you where to find that information and how to read it.
Open an integration's details
Go to Flows > Integrations in the left-hand menu and open the card for the integration you want to inspect. This opens the integration's details panel, showing its category, description and overview.
Next to the Reconfigure button, click the three dots to open the actions menu:
View configuration shows the current settings of the instance.
View details opens the integration details from which you can view execution history and logs.
Pause Flow temporarily stops the instance from running without losing its configuration.
Deactivate Flow removes the instance.
View details > Logs is the main tool for troubleshooting.
View executions and logs
View details opens a panel with tabs. The instance's current running status is shown next to its name.
Executions
The Executions tab lists each run of the instance, most recent first. Every entry shows a status indicator, the timestamp and how long the run took. Select a run to open its Execution Details, which identify the instance, the flow that ran and the instance type.
Within a selected run you can switch between Logs, Step Outputs, Linked Executions and Retry. Step Outputs shows what each step produced, which is the quickest way to see where a run diverged from what you expected. Retry re-runs the execution.
Logs
The Logs tab shows a combined log across the instance's flows. Each row lists the timestamp, the type, the flow, the relevant config variable and the message. Use Search logs to find a specific entry, Filter to narrow by type or flow, and Refresh to pull the latest entries.
Reading the messages tells you when each flow started and ended and what happened in between, which is usually enough to understand why an instance did or did not do something.
Tip: When you contact support about a flow, include the timestamp of the run, the execution ID and the execution log. That lets us find the exact execution quickly.
Empty dropdowns during configuration
Some configuration steps ask you to choose a value from a dropdown, for example a pipeline. If a dropdown is empty, it means the underlying object does not exist in your account yet. An empty pipeline dropdown, for instance, means there is no pipeline for the integration to use.
When this happens, leave the configuration wizard, create the missing object (the pipeline, in this example), then return to the integration and reconfigure it. The dropdown will now list the value you created.
Important: An empty dropdown is not a bug. It means the value it should list does not exist yet. Create it first, then come back to the configuration.