Automations are the main backend tool to do any data manipulation/check outside of the User operating screen (Tulip Player) and, as it has already been highlighted, automations have quite some restrictions (most likely to limit the bandwidth use on Tulip servers).
Would it be possible, in the future, to deploy an On Premise Automation Host in a similar way to the On Premise Connector Host. This “OPAH” would have less restriction in the use of timer and frequency of checks, no restriction on the number of tasks, no restriction on amount of email sent (just seen this post) and it would only use the local server resources to process those tasks.
I would imagine that the same “OPAH” could also process the new “functions” that are coming.
Hi @kefl great question! Running into the current platform limits is a great sign of value for the feature. We love to hear that features are increasingly valuable, and we want to work together to ensure that limits are safe but not hindering.
For Customers - if you’re running into a limit with Automations, please work with your customer success manager. Our platform is theoretically scalable and we can work with you to understand the limitations and either optimize the Automation or capture the need and work towards increasing limits (some infra investment may be needed)
For Partners - please also work with us on the use cases and scale you’re seeing. Automations have to run in the cloud to write to Tables etc, so we have not yet considered On Prem, but we’ll take it into consideration. Independent of hosting, some server limits would be necessary - the question is where to draw the line. Right now we have some nominal platform limits, but these can be increased with the right business case. We would be happy to discuss your case on a call if that’s helpful! viz @seb.lorandel