name conflicts when creating a brand new resource…where there DEFINITELY isn’t an existing resource with that name?
q
quiet-wolf-18467
03/22/2022, 9:40 AM
Are you creating this resource in some kind of function or loop that is created multiple times? Can you share the code, please?
f
famous-salesclerk-74711
04/06/2022, 10:10 PM
hey @quiet-wolf-18467 - sorry about the wait. it turns out - you were absolutely right, this was because we used a constant name for resources created in a loop 🤦♂️ thank you!