Hi All,
I'm trying to send a CSV report attachment via delivery. It works fine for some days, and some days the report is getting triggered as a blank CSV file, even though my workflow has count. If I trigger it again, I'm getting a proper report. Why is this happening? Any solution to this issue would be appreciated. This is happening in Adobe campaign classic version 7
Regards,
Sujith kumar
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hello @Sujith_02kumar ,
If you are operating in a multi-server instance (with two or more wkserver), the issue may arise due to a discrepancy between the server where the file is generated and the server responsible for preparing the delivery. It's apparent that the second server cannot locate your CSV file, which results in the transmission of a blank file. The instances when it does work occur when your CSV file is generated on the same server responsible for preparing your delivery.
A viable solution for this situation is to ensure the generation of your CSV file to a shared storage folder, such as a Network Attached Storage (NAS), to ensure accessibility for all servers.
Best regards,
Amine
Views
Replies
Total Likes
Hello @Sujith_02kumar
Are you using the same way to share reports from multiple workflows?
If that is the case, then I assume you are using the same file name in all workflows, and they are overwriting the data. To fix this, make sure all workflows are using different file names.
Views
Replies
Total Likes
Hi @_Manoj_Kumar_ ,
I'm using different file name but the recurring delivery which I'm using is copied from other workflow. I can't understand sometimes it works fine and sometimes I'm getting blank report even though my workflow has count
Views
Replies
Total Likes
Views
Replies
Total Likes
Hello @Sujith_02kumar ,
If you are operating in a multi-server instance (with two or more wkserver), the issue may arise due to a discrepancy between the server where the file is generated and the server responsible for preparing the delivery. It's apparent that the second server cannot locate your CSV file, which results in the transmission of a blank file. The instances when it does work occur when your CSV file is generated on the same server responsible for preparing your delivery.
A viable solution for this situation is to ensure the generation of your CSV file to a shared storage folder, such as a Network Attached Storage (NAS), to ensure accessibility for all servers.
Best regards,
Amine
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies