Hello AutoCrat team,
I’m hoping you can help us diagnose what appears to be an issue with one of our scheduled merge jobs.
We have built a workflow that generates individualized PDF reports from a Google Sheets workbook. The merge source is a formula-driven sheet rather than a manually maintained table.
The first column of the merge sheet is generated by the following formula:
=SORT(UNIQUE(FILTER(Reports!A2:A,Reports!A2:A<>””)))
The remaining columns contain formulas that derive each participant’s report content from that unique list.
The job behaved correctly for approximately 11 hours after launch. Without any changes to the spreadsheet, merge template, AutoCrat configuration, or trigger settings, the scheduled job began behaving differently overnight.
The symptoms were:
After carefully reviewing the generated reports and email logs, we do not believe participants received one another’s reports. The reports appear to have been delivered to the correct recipients. The issue seems to involve row selection and/or merge bookkeeping rather than incorrect report delivery.
Could the use of a dynamically generated merge source (using the formula above) contribute to this behavior? If so, would you recommend using a static values-only sheet as the merge source for scheduled jobs?
If you have a private email address, we’re happy to provide additional details, screenshots of the job configuration, or a simplified example workbook if that would be helpful.
Thank you very much for your assistance.
Sincerely,
Jason Patent