I wanted to know if there is any limitation in the creation of subitem,
I need to create 57 subitem, create normal up to subitem 53, then return the following error:
{ errors: [ ‘Not Authenticated’ ] }
This is the mutation i’m using:
const query = mutation { create_subitem (parent_item_id: ${itemId}, item_name: "${nomeSubItem}") { id, board { id } } };
There should not be a limit to how many subitems you’re able to create. I tested this myself and was not able to recreate the same issue.
How are you creating these subitems? Do you have a function that’s looping through and creating these subitems in the span of let’s say 5-10 minutes? Or are you creating these subitems over long stretches of time, by hand?
Does this behavior also occur for different items? Or just a single item? What about different boards?
I’m curious to learn more and see why this might be occurring for you…
Hi, Sorry for the delay.
let templete = [‘0-Recebido de peça padrão’,‘1-Digitalização de peça padrão’,
'2-coleta dados técnicos peça padrão','3-Abrir projeto no sistema de gestão','4-Gerar dossier produto',
'5-Estudo saveglass','6-Solicita PLM INTERNACIONAL','7-Criação apresentação do projeto',
'8-Criação/atualização de estrutura no PDM','9-Kick-Off','10-Armazenamento peça padrão e identificação',
'11-Criação de cronograma','12-Definição de processo pré-montagem','13-Previsto no budget',
'14-Viabilidade produtiva','15-Definição de ferramenta','16-Mapeamento homologação','17-Solicitações CAD/ferramental',
'18-Criação da BOM e roteiro','19-Saveglass','20-Programa de acorte','21-Plotter para corte','22-corte de peça padrão',
'23-confecção do fatolito','24-Impressão/Validação do fotolito','25-Impressão para estiragem BANDA',
'26-Gabarito de controle','27-Ferramental modelamental','28-Construção ferramentais','29-AP3-Zona de visão',
'30-Chapelona de logotipo','31-Chapelona de pré-montagem','32-Definição de embalagem','33-Criar codigo argis para integração pedido',
'34-Inserir pedido de compras autover','35-Ficha técnica-vidro base','36-Ficha técnica-vidro pré-montagem',
'37-Criar VL10i/VD52','38-Criação do trello-Amostrar','39-RAA-Agendamento','40-Produção de amostra',
'41-Pré-montagem para teste laboratório','42-Aprovação tridimensional','43-Validação laborat ório',
'44-Homologação','45-Emissão de-PSW','46-Aprovação autover-PSW','47-Teste de montagem',
'48-Pré-montagem de todas as peças de amostra','54-Transferência para FER1',
'55-Transferência para autover','56-Lançamento do produto autover'];
for (let contador = 0; contador < templete.length; contador++) {
console.log("Inside the for")
let nomeSubItem = templete[Number(contador)]
await mondayService.criandoSubItems(shortLivedToken, item, nomeSubItem);
console.log(nomeSubItem)
}
return res.status(200).send({ message: "sucesso" })
This code base, ‘criandoSubItems’ is where I call mutation. The parameter ‘item’ is the id of the parent item, and the parameter ‘nomeSubItem’ is where I define the name of the subitems.
Because there are many subitems, do I need to delay the creation?
I tested this problem on two different accounts, on my company’s internal board and on the client’s.
Thank you for your attention!
Thank you for getting back to me!
I am tempted to say that what you’re running into here is a race condition issue, which happens when you try to create too many objects (be it items, columns, boards, etc) at once. However, the error message throws me off.
Do you mind letting me know the name of these accounts that are experiencing this issue, as well as a time frame for the most recent occurrence? This way I can check our logs too and see what I find.
I see, the one I have access to now is “desenvolvimento-agr”
I just ran the code to create new logs, so you can find it faster (14:31: Brasilia Time (BRT)
I can’t seem to find the account. Your account name should be whatever is in from of “.monday.com” in the URL.
For instance, if your account is “EXAMPLE.monday.com,” the account name is “EXAMPLE.”
Let me know-- thanks!
That’s so weird… Okay let’s try a different way. What is the email associated with this account?
The email that is linked is:karla.moncayo@sinergis.com.br
Thank you, I was able to find it.
Okay, I see an error in our logs and I think we should submit a bug report. As such, I just need some additional information from you:
I know that this is a lot of information, but all of it will be relevant for inclusion and for our developers to understand the background issues that could be present.
Thank you for working with us on this issue!
Hi Helen,
Could you give me a prediction about this? I have to give feedback to my client.
Thank you for your help.
Thank you so much @franklin.oliveira!
I just submitted a bug report for our developers. I will let you know as soon as they get back to me with an update.
Is your app an integration or a board view? If it’s an integration and you’re using the shortLivedtoken, this will only be valid for 1 minute which could be why your requests are always timing out then!
My app is an integration, but I didn’t know about this information about visualization, great to know!
An addendum, the code is running locally, do I need to leave it running?
Hi @franklin.oliveira, apologies, it’s integrations not board views where the shortLivedToken is only valid for 1 minute, so this makes sense!
In this case, I would utilize a different authentication method, perhaps implementing OAuth instead so that you have access to a token for a longer period of time.
Here is our article on implementing authorization for integration recipes: https://monday.com/developers/apps/integration-authorization/.
I hope this helps!
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
