I know this is technically not the place for it bu...
# general
b
I know this is technically not the place for it but is anyone else having issues with Celigo? All of our flows (most of which are to or from NetSuite) are stuck In Progress. I opened a ticket but haven't heard anything yet.
v
We're also having issues with a few, no errors or anything, just seemingly stuck not processing
a
not good, their status.celigo.com page doesn't say anything yet
b
I opened an urgent ticket with them. I'll let you know what I hear back
r
Checking with the team. @matt.graney @Tyler Lamparter
b
They have admitted that they have received multiple requests with the same issue.
t
This is currently affecting many customers. The status page will be updated soon to reflect and engineering is actively trying to resolve the issue. Will report back when I know some more.
b
Thank you for the update Tyler.
@Tyler Lamparter what is the urgency / ticket level and SLA for a turnaround time? My team is unable to process 20 million dollars worth of payments today and if this lasts until tomorrow we will be unable to process 45 million dollars worth.
t
This is a P1 incident that engineering is working quickly to resolve. Our key engineers are working on it, and the team will continue to work until it's resolved.
The priority couldn't be higher for us.
b
I appreciate the feedback and the availability to respond Tyler. I have subscribed to the status page but there has not been much in the way of updates. Like many customers we have until 10pm EST to deliver our payment files to our bank which we utilize Celigo to do. I need to share with our executives if this is at risk .
a
Does it have anything to do with the new requirement of the ns_at parameter when requesting to Suitelets from outside of NetSuite?
t
It's not new, 2024.2 has been out for months.
t
@Brendan Altman we aren't able to provide an eta at this time.
And this is not related to NetSuite.
t
My flows seem to be running now.
t
@Brendan Altman are your flows running now?
1
There was a connectivity issue between our workers and the Kafka queue which then led to the queue piling up and little to nothing being processed. Just about everything should be running now