Knack Tasks: Best Practices
- Dave Parrish
- Mar 22
- 3 min read
A few years ago, scheduled tasks in Knack weren’t always consistent. They sometimes failed to run, which was a big deal if you were relying on automation. But to their credit, the platform improved a lot, and now scheduled tasks are very reliable.
Even so, I’ve learned there are some best practices you should follow — especially if you’re running a lot of automated tasks.
Let me walk you through a real-world use case and how I handled it.
The Use Case: Automating Member Reports
I was working with a trade association that had about 1,000 members. Each member had a Terms Code that determined when they needed to submit a report and pay dues.
The payment schedule varied by member:
Monthly
Quarterly
Annually
Specific months (January, February, May, etc.)
What we wanted was this:
On the scheduled date, a report is automatically created in the member’s account.
Then member receives an email notification telling them the report is ready.
The member logs in, fills out the report, submits it, and pays online.
All automated. No manual work.
Prior to this, they were having all reports and payments go to a post office box, then manually reviewing all the reports, and physically going to the bank to make deposits. : (
How I Built It
To make this work natively inside Knack, I had to create multiple scheduled tasks — one for each scenario.
For example:
If a member’s Terms Code = January
And the current month = January
And the member is enrolled in the online reporting program
Then → Create a new report and attach it to that member’s account
That handles report creation.
Then I duplicated those scenarios again, but instead of creating a report, those tasks send the email notification.
In total, this system ended up with 34 scheduled tasks.
It sounds like a lot, but it works — and it works well.
The Most Important Lesson: Don’t Run Tasks All at Once
This is critical.
You don’t want too many tasks running at the exact same time. So here’s what I did:
Report creation tasks run on the 19th of the month, spread out at different times throughout the day.
Email notification tasks run on the 20th of the month, also spread out at different times.
This spacing prevents the system from trying to do everything at once. It looks something like this:
What Knack Told Me About Task Limits
I actually asked Knack support about this and explained my use case. Here’s what they confirmed:
There is no limit to how many scheduled tasks you can have.
However, only 4 tasks run concurrently at any given time.
If more than 4 tasks are scheduled at the same time, the others will wait in a queue until one finishes.
They also confirmed that the approach I used — spacing tasks out across different times — is the recommended best practice.
Wrap Up
That’s my setup, and it’s been working great.If you’re automating reports, invoices, renewals, or reminders in Knack, this approach is solid and reliable.
Thanks for reading, and I hope this helps you build better automations in Knack.
Interested in my Knack database services? ... Book a call with me here: https://calendly.com/daveparrish/callwithdave
Comments