You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When running actions that use a large amount of memory or run for a long amount of time, they often fail. This is due to the fact that actions are currently run using the actionRunner cloud function, which can easily time out or use all of its memory
Describe the solution you'd like
"Runner Type" dropdown that would allow the user running the action to specify a more robust runner
Additional context
Something else to keep in mind is that this may want to be part of the action template as well as the ability to edit this. For example - when making an action template that requires many collections to be copied, the template should be able to dictate a runner that can handle long running time as well as not allow the user to change this (since it could cause that action to fail).
The amount of runs per user and project should be tracked as well since running dedicated VMs can rack up price quickly. In the future it should be easy enough to limit the usage of dedicated resources based on a payment plan.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When running actions that use a large amount of memory or run for a long amount of time, they often fail. This is due to the fact that actions are currently run using the
actionRunner
cloud function, which can easily time out or use all of its memoryDescribe the solution you'd like
"Runner Type" dropdown that would allow the user running the action to specify a more robust runner
Additional context
Something else to keep in mind is that this may want to be part of the action template as well as the ability to edit this. For example - when making an action template that requires many collections to be copied, the template should be able to dictate a runner that can handle long running time as well as not allow the user to change this (since it could cause that action to fail).
The amount of runs per user and project should be tracked as well since running dedicated VMs can rack up price quickly. In the future it should be easy enough to limit the usage of dedicated resources based on a payment plan.
The text was updated successfully, but these errors were encountered: