feat: increase the number of task executor instances#1613
Merged
davidgamez merged 1 commit intomainfrom Mar 6, 2026
Merged
Conversation
Member
Author
jcpitre
approved these changes
Mar 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Summary:
This PR increases the number of instances that can run concurrently with the task executor function. As the task executor function is a
genericcloud run function, there is no point in limiting how many instances can be run at a single point in time. I set it to a high number(200), to avoid over-billing in case of a code error on the caller.Expected behavior:
The number of max instances must be set to 200.
Testing tips:
Just check the DEV environment settings.
Please make sure these boxes are checked before submitting your pull request - thanks!
./scripts/api-tests.shto make sure you didn't break anything