Cartodb: 4096 named maps per account limit is not working

[noguerol]

Context

Based on https://github.com/CartoDB/support/issues/733 it seems the 4096 max named map limit per account is not working when reached.

cc @kevin-reilly

[kevin-reilly]

Digging through the notes and talking to Stephanie, it seems like the root of the issue is that they are not able to create a named map through the API because of the limit. But they are able to create a named map in Editor.

So, either the API is wrong or Editor is not respecting the limits.

[zingbot]

I'm following up on this issue for the customer affected. Any resolution on this? I want to keep them informed.

[zingbot]

Here's the comment from the customer on how it is affecting them right now.

"The issue isn't affecting our users right now - we found a workaround for the client who needed a persistent link to tiles. We don't really use named maps in MapGeo right now. We are concerned about our account management. From what I understand the combination of layers & visualizations contribute to the named map count (& we are well over that) so we want to figure out the best way to manage our account/data"

[kevin-reilly]

@dgaubert Can you look at this issue? Is this something we can fix easily?

[dgaubert]

Yes, I can.

I don't know if it's easy to fix or isn't, I need to figure out what's going on.

[kevin-reilly]

@zingbot Just to confirm here, this issue seems to have two parts:

1. They are hitting the limit of 4096 maps but it isn't preventing them from creating more maps.
2. They need to be able to create more than 4096 maps.

If we fix the problem in part 1, they won't be able to create maps.

If the work around is working, can we just let this lay? What is their concern if it is not impacting them? What are they worried about in terms of creating and managing data?

[zingbot]

I'm calling her to get a better idea of the risks in not doing anything. Thanks for asking, @kevin-reilly

[zingbot]

Ok, so they have a workaround and we can consider the problem stable. What we've agreed to do is to let it lie until Q4 and see if it comes up again. It might be cleared up by changes down the road. I'll keep it in my notes if it comes up in the meantime.

Thanks for looking into this, everyone.

[zingbot]

Temporarily resolved.