Skip to main content

Hi everyone,

I’m Darshan Hiranandani, encountering an issue where process data is not being transmitted to Insight, despite the process running successfully. The process executes as expected, but no data points are generated, which happens frequently, often with a 50/50 occurrence. This has made the Insight reports unreliable.

I have a bot that runs twice a day in a production environment, and while some data comes through fine, there are gaps, and specific days, like 11.11, don’t show up in Insight, even though the log files clearly show the data was processed.

Here’s an example:

  • 11.11 07:00: Process started “variable” “day started”
  • 11.11 09:00: Process started “variable” “OK”

But in Insight, only the 18.11 data shows up, and the 11.11 07:00 entry is missing.

I’m wondering if there are known issues that could cause missing or corrupted data, such as special characters or other factors. The code runs through the analyze steps correctly, and I have a log file confirming the data is being generated at the right stages.

Has anyone experienced this or have suggestions on what could be causing this? I’m trying to pinpoint why certain data points are missing from Insight while others are fine.

Any help or insights would be appreciated!

Regards

Darshan Hiranandani

The only thing I can think of is if the flow of your automation isn’t executing the Analyze: Close action, or that your session name doesn’t match the Analyze: Open.

Maybe try a simple bot that you can execute occasionally to see if it is reliably logging the data.

Hello Darshan, my name is Megha. The issue of missing data points in Insight, despite successful process execution, could stem from several potential causes. One common culprit is the transmission process between the bot and Insight, where intermittent network issues or timeouts might prevent data from being recorded. Additionally, special characters or unexpected formats in the data could lead to parsing errors on Insight's side, causing some entries to be rejected silently. Another possibility is discrepancies in time zone configurations, which might misalign the timestamps in your logs with those in Insight. To pinpoint the problem, verify that all data is being successfully transmitted by monitoring network logs or API responses during the process. Check Insight's error logs or validation rules for signs of rejected or incomplete data entries. If special characters or formatting is suspected, sanitize the input data and test it in controlled scenarios. Collaborating with your Insight support team can also help identify if the issue is related to platform-specific limitations or known bugs.

Hope this helps, thank you!

Reply


Terms & ConditionsCookie settings