rackem
Well-Known Member
I have a Scheduled Task that cycles through and processes a large table of records in batches. The results were inconsistent and during troubleshooting I found that some records were processed more than once and nearly at the same time. This only occurred if the Task ran automatically versus manually. I think the Fabrik Scheduled Task occasionally launches multiple instances when it is triggered by a site visit.
I was able to create a workaround in my code to make sure only one instance could run at a time by first assigning a unique id to a database field, reading it back from the database, and verifying it matched, before running my desired code.
Has anyone else run across this? I assume this is not intended Fabrik behavior but also probably does not affect many people.
I was able to create a workaround in my code to make sure only one instance could run at a time by first assigning a unique id to a database field, reading it back from the database, and verifying it matched, before running my desired code.
Has anyone else run across this? I assume this is not intended Fabrik behavior but also probably does not affect many people.