I have a list of 1 500 line with email and names, filled with a form.
I want to generate a pdf receipt for each line, then to email this pdf.
I have a seatable enterprise self hosted.
So I’ve made a automation rule to generate the pdf and another automation to email it to each people.
sadly, this automation is reaching the 50 limit and therefore runs only once a day.
That means it would take a month for the server to create and send these receipt, which is not ok.
how to circumvent this issue ?
How could we run the automation rule every hour or every 10 minutes ??
thanks
The fact, there is a automation limit by SeaTable was well known. However, 50 automations per minute is not very much.
For example, we have 200 rows added weekly to a base. Then we have to make 4 calcualtions per row, results in 800 automations. With SeaTable this is currently not working, as the limit is 50. When working in the app, we can not use the button to initiate this manually. We, started to copy the automation, and execute it several times a day. But this way, we need a couple of ours until each row is fully calculated.
Is this what you refer to as “large inputs” in your previous post? This is 6-7 rows per day. With respect, but this is not testing the limits of SeaTable - SeaTable Cloud or SeaTable self-hosted.
With a script run (= automation run) you can complete all but uncountable number of calculations within seconds. Please look into this.
I don’t know your use case, but I struggle to make sense of what you say: 800 automation runs per week when SeaTable Cloud’s limit is 50/min, how can this result in “we need a couple of hours until each row is fully calculated”?
This is not the idea and quite likely the result of a bad data model. If you run the automation 4 times, that’s ok. But if you feel like running it more frequently, please don’t do that and revisit your data modell.
@rdb In our case, we have a pdf to generate for each line. PDF generation takes around 10 seconds. so I’m ok if the server generates all pdf for the 1 500 lines in 4 hours, but It won’t, as it will only generate the first 50, then wait for the following day to generate 50 additional.
If i put 1500 as automation limit, will the server perform 1500 in a row ?
What are the side effects of this ? the server will be at 100% generating the pdf for 4 hours, then won’t be useable for other people ?
Hi Ben,
Of course this is not a proper SeaTable solution, but maybe you can use n8n for this purpose (I don’t know if you already use it but “installing” it on SeaTable self-hosted enterprise edition is pretty straightforward): I’m not sure I figure your whole use case out, but you can probably create a n8n workflow with the run frequency you need and make it modify something in SeaTable, being detected by your automation so it can run more frequently…
Another “not-SeaTable-at-all” solution that I sometimes use is to generate your docs via the pytohn docxtpl library which uses docx templates to generate docs depending on your data. It needs some coding experience and is a bit heavy to set up (the lib doesn’t directly generate pdf files, so you’ll have to install something like libreoffice-headless to be able to convert your doc to pdf), but if you’re interested feel free to contact me, I can show you how I used it in several projects.
Hello.
I’ve added the line to the dtable-events.conf file as :
[AUTOMATION]
per_minute_trigger_limit = 1000
located here : /opt/seatable-server/seatable/conf/
One automation has to send emails and I have around 300 email to send.
But seatable sends only 50 and keeps mentioning the limit of 50 per minute.
how to debug @rdb ?
Hi,
the first option doesn’t work, as the pdf creation is restricted to only to few automation pattern.
It’s only available in the “execute routinely…” not in the “execute when a field has been updated”
and correct me if I’m wrong, but n8n doesn’t allow to trigger automation.
and scripting in python kills the no-code solution… It has to work for my assistant.
Hi Ben, sorry to hear it’s not working : I didn’t noticed that the “generate pdf” action was not available for every trigger, and no, you’re right: as far as I know, n8n can’t trigger directly a SeaTable automation.
You might eventually find a solution by generating your pdf directly with n8n: I heard about people using gotenberg for doing so, or there are some (paid) services like docugenerate that can be used from within n8n with api calls, but of course it will need some extra work compared to the solution of generating your pdfs from your already existing templates from the Page Design plugin…
The 50 limit is that the automation rule can only handle 50 rows of matched records.
It is not it can only run 50 times in a minute.
The solution is that you use a rule that filter out the rows that already done. So the next time the automation rule will pick another 50 rows in your table.
@daniel.pan i do that already.
But i’m limited by the delay between each automation, as the shortest between two occurrence is one day !
The pdf generation is not available in all automation triggers. And i can therefore perform only 50 items every day !
Final word on that with the actual situation : duplicating the automation rule to have it triggered every hour allows to reach an acceptable 1200 rows per hour (50*24)
1 Like
Do it like thousands of other people who have used SeaTable to develop powerful processes and get their ideas and tasks done more efficiently.
: I didn’t noticed that the “generate pdf” action was not available for every trigger, and no, you’re right: as far as I know, n8n can’t trigger directly a SeaTable automation.