We have detailed logging and debug enabled on a flow and for some reason, some records show trace log info and some do not. In the example below, there is no information available and clicking on the open trace view results in a page that continually loads/refreshes with no data. Does this have something to do with the trace key saying "Not Available"? And, if so, why is it not available?
What you’re seeing with “Trace key: Not Available” means the system wasn’t able to identify a unique value for that record at runtime. The trace key is what enables the trace view to correlate activity across steps for a single record. When it’s not available, the system cannot construct the trace view, so instead you’ll only see logs at the individual step level for that record.
To make this more consistent, it’s best to explicitly configure a custom trace key so every record has a reliable identifier. You can follow the guidance here to set one up: https://docs.celigo.com/hc/en-us/articles/360060740672-Set-a-custom-trace-key-to-uniquely-identify-a-record#set-a-custom-trace-key-to-uniquely-identify-a-record-0
That said, not having a trace key does not prevent logs from being captured. Logs are still generated at the step level and should be visible even without a trace key. If you’re seeing some records with no logs at all, it’s usually due to known logging limitations (for example, certain steps/connectors or scenarios where logs may not be persisted). You can review those under limitations here: https://docs.celigo.com/hc/en-us/articles/45404136636699-Introduction-to-execution-logs#flow-run-logs-2
If your specific flow/step doesn’t seem to fall under any of those scenarios, it would be best to raise a support ticket so the team can take a closer look.
Hope this helps.
@praveenbasani - Thank you, that was helpful. I was able to get the parent export to produce a trace key for every record now. I still have a few questions/comments about this.
I noticed that some of the steps in the flow that produce child records resulted in odd trace keys, so I added child trace key overrides to those steps as well. The trace view (debug) UI could use some improvement so that the child trace key column is able to be expanded. Right now, the only way to see the full value of the child trace key is to hover over it as shown below.
Also, can you help me to figure out how to view the record running through the entire flow? When I tested this new logging functionality on a different flow a few months ago, I was able to see the record as it flowed through every step of the flow. In this case, it is all broken up and I can see bits and pieces, depending on which step I click on the logs. I can't find the "overall" view with all the steps, branches, etc. similar to the screenshot below from the documentation. What am I missing?
Overview of our flow, with lots of branches going on:
We don't get a single view of a record passing through all the steps/branches. This is what I get from the "run level" debug log and then each of these has its own smaller subset of logs rather than one comprehensive view of the entire flow. Hopefully what I'm saying makes sense.
What you’re describing is typically seen when the flow contains steps that use connectors other than NetSuite or HTTP. The “end-to-end” trace view shown in the documentation relies on execution logging support across all steps in the flow, and at the moment, that level of tracing is only supported for certain connectors like NetSuite and HTTP.
If your flow includes steps using other connection types, the platform won’t be able to construct that unified, record-level trace view. Instead, the execution details are available only at the individual step level, which is why you’re seeing the logs broken up rather than as a single, continuous flow. We are actively working on expanding support to additional connectors so that more flows can benefit from the full trace view experience over time.
Also, thanks for your feedback on the UI for child trace key column. We will work on improving this experience.