Not sure if anyone has the same problem but we are seeing more of these bugs/error with the recent package update of excel activity.
From time to time excel scope activity will throw an error and replaces the existing excel log file with Empty data. it’s a major bug as we lost all the logs data and have to check the log message manually for each of the completed transactions to avoid redoing it again.
I can see that we are not the only ones having this issue. this bug/issue goes back since 2018
@whitestar How do you write the data in an excel. Is it using data table. if that is the case make sure the data table has data. Also, the what is the version of excel activities that you are using
In each execution during the Write Cell activity are you getting this error? Or only sometimes while using Write Cell?
As you mentioned the issue is happening only for some execution is strange. Is it a new workflow recently created or are you facing the issue in the existing workflow after the package upgradation?
it’s not limited only to excel write cell activity I was giving an example.
It’s an existing workflow/new workflow that can happen anytime. it has happened in the past as well. I just didn’t ask here as it happened very rarely.
With those types of bugs, a project that reproduces the issue, even if inconsistently, is much appreciated
Any chance you could create a share a zip of such a dummy, sample project?
The technical support couldn’t figure out the problem as it was very hard to duplicate the issue.
However, I figured out the issues at least for our case. Can’t promise this will work for your issue.
We save our working excel file in a shared network drive. This problem usually occurred when the bot has to save multiple excel cell values in one workflow or read/write an excel file in very short intervals between each excel scope workflow.
I moved the working excel file from the shared network drive to the Local Drive during the process run time. This solved our issue.
I suspected this was due to network delay and the excel file couldn’t save/close in time.
Thanks for your reply and the tip.
Recently, we have indeed encountered network slowdowns.
Even if the context is not the same (we are not writing any data, only reading a configuration file), I will copy the file locally before starting the process.