Guys, can NS integrations be removed? I can't find...
# suitescript
m
Guys, can NS integrations be removed? I can't find a way to delete them.
b
m
I saw that page, but it is weird. I am asking the support about it now. Because making the integration as blocked, makes it still reserve the same concurrency unit.
b
that sounds strange, but you can set the concurrent limits on the integration record before blocking it
m
message has been deleted
It can't be zero
b
empty value
it might not actually matter, it looks like other integrations have reserved all the concurrency slots avaialble
m
It is all strange, when I removed the value, the record accepted it, saved it, but still there is unallocated unit.
b
that sounds like whats supposed to happen, so im not really sure what you are describing
m
message has been deleted
Because there is unallocated unit, I expect the max limit to be 5, to be able to set it to 5
But I can't, it is still 4
b
what does Integration Governance show you
m
message has been deleted
b
that looks reasonable
you assigned all your concurrency slots
there is no more left to assign
m
So what does Unallocated Concurrency Limit mean?
b
m
Oh, I understand now, but why? Why can't I consume all of them?
b
i mean if you wanted to, you probably want to just block all the other integrations
m
I already did that, but the docs says
The value of the MAX Concurrency Limit field is always one less than the total unallocated concurrency limit of the account.
Not sure why
message has been deleted
this is very bad, right?
b
as in if you left no concurrency slots for other integrations, they would always fail
if you wanted them to always fail, you probably want to just block them
m
I already blocked all of them except one, but I can't assign all 5 units to that one.
b
you dont need to if its the only one making requests
it has access to all 5 without using concurrency limits
m
I didn't know that, thanks. That image above means we have a serious problem with concurrency, right?
b
honestly it depends
a proper integration is designed to retry on concurrency related errors
so at worst, it would just take longer to do its job
m
It is a shipping company, and the most critical endpoint is the one recording the shipments, and it is like 4K shipments per day
b
it becomes a problem when your account can no longer handle requests faster than they are queued
m
Yeah, I am discussing making a retry mechanism with them.
b
or if there is a time sensitive nature to those requests and the queue becomes longer than that time
m
Will discuss this with them, or they can talk to Oracle about buying more units. Thanks for your help ❤️
b
alternative solution is to implement the concurrency limit on the integration side so that it can limit how many requests it sends at the same time
still generally involves implementing a queue
m
Yes, that would be cleaner I guess
b
it what you would need to do if you wished to use the concurrency limit on the integration record