has been reached.' Why am I getting this message? Also is this related to another message I get when trying to Add another Environment I get 'Environment limit reached'?
Hi @DF214566​,
Ahhhh, the infamous maximum number of environments error. Yes, this is related to both of your issues you mentioned. I have had an ongoing conversation with Matillion in regards to this limit as it's not clear what it means, why you get it and the purpose for it's use.
Long story short there are 2 main reasons this was created. The first reason was that when Matillion was created they needed a way to control how much product utilization you get for the price they are charging. What also ties into that rather tightly is that Matillion also needed a way to ensure users were not going to overload and crash the instance. This could be done by creating say 100 projects and having all of them scheduled to run at that exact same time. So, they built in a 15 environment limit on the Matillion instance to ensure both of the above. There are lots of arguments to be made on both sides as to whether this is the right way to control this or not. There is something on Matillion's roadmap and I do believe they plan on changing/addressing that but for now you are limited to 15 environments across all projects on a single instance.
Once you hit that limit you will start getting the error you mentioned and it will not allow you to create any more environments. I would contact your Matillion rep and explain your situation. They may have some suggestions for you based on your situation. Most of the time they will ask if you can consolidate your projects because if you can do that then you will need less environments. This doesn't work for everyone and we were one of those cases. There could be options to increase the environment size as well but I believe there could be cost implications.
One thing that we were doing which led to us hitting the limit was creating Test projects for our devs to play in without effecting other projects. If you have 10 devs and each one has a Test project which has at least 1 environment, you can see how you would run out of environments fairly quickly. To get around this, we started using one of our existing projects and creating a version for each developer in that project. Once you create the version the dev could go into their version, delete everything out of it, create test orchestrations, etc. and just pigging back off the environment in that project. This is where versions are nice because it doesn't effect the Default or any other version of that project.
I hope this helps shed some light on what you are experiencing. Let us know if you want more detail around this. Thanks for posting!
​Hi @Bryan​,
Thanks for your reply. Is the number of environments based on projects or jobs you have in a project? I don't see us reaching that 15 environment limit if it's based on project, currently we only have maybe 6 or 7 projects and 3 separate environment based on which project your in. Thanks in advance.
Hi @DF214566​ ,
The 15 environment limit is across all projects on the whole instance. Based on the numbers you just provided you would have 6 or 7 projects times 3 environments. This would mean, 6x3=18 or 7x3= 21 either way you are way over the 15 environment mark. So, I am guessing maybe 1 or 2 of those projects have 1 or 2 environments instead of the 3? Either way, unless something has changed in the last couple versions the limit is 15 environments across everything on your Matillion instance. It's not convenient but it's what we have to work with right now.
If you feel like you are well under that 15 environment limit, you might reach out to support and ask if they can help you understand why you are hitting the limit. I hope this helps you.