Post-Release Issue with Celigo Flow and Ticket Submission Problems
Hi,
I'm reaching out because I've encountered a critical issue with my Celigo flow following the recent release.
I've been using this particular flow daily without any problems until now. After the release, I set up the resources for an export, previewed the data, and everything appeared to be in order. I saved the configuration and ran the flow, but afterward, no data was picked up. When I checked the settings again, I found that the resources had reset to their default state, even though I had configured them correctly. This is the first time I've experienced something like this, and it's quite puzzling. I’ve attached screenshots showing the issue for reference.
To resolve this, I tried to submit a support ticket through the partner portal. However, when I attempted to open the project "Clientname," I was met with a 404 not found error. I then tried to submit the ticket using the old method, but it couldn't. As a result, I had no choice but to bring this issue to the community in the hope of finding a solution.
Reopen flow step:
Comments
Hi Nuri Ensing,
Could you please share the screenshot of the audit logs for the export and flow, after masking PII data.
Thanks.
Hi John,
Debug connection log on first step:
08/21/2024 11:15:55 am 388fca09e54e4e44a67baf6f49958d4c export 66866c73a9437e14eb5dad80
{
"url": "https://*************/b1s/v1/BusinessPartners('C6587')",
"method": "GET",
"headers": {
"Cookie": "********",
"accept": "application/json"
}
}
08/21/2024 11:15:55 am 388fca09e54e4e44a67baf6f49958d4c export 66866c73a9437e14eb5dad80
{
"headers": {
"date": "Wed, 21 Aug 2024 09:15:53 GMT",
"server": "Apache/2.4.56 (Unix)",
"dataserviceversion": "3.0",
"content-type": "application/json;odata=minimalmetadata;charset=utf-8",
"vary": "Accept-Encoding",
"etag": "W/\"D02560DD9D7DB4467627745BD6701E809FFCA6E3\"",
"connection": "close",
"transfer-encoding": "chunked"
},
"body": {
"odata.metadata": "https://*************/b1s/v1/$metadata#BusinessPartners/@Element",
"odata.etag": "W/\"D02560DD9D7DB4467627745BD6701E809FFCA6E3\"",
"CardCode": "C6587",
// (Other fields omitted)
}
}
Nuri Ensing, Thanks for posting this to the community. I've opened a ticket, so Support can assist with this.
Hi Nuri,
We were able to reproduce the issue where the UI doesn’t display the Resource and Endpoint values after updating and saving. However, you can still view the relativeURI or parameters by switching to the HTTP view. Flow runs and previews should work as expected. Could you please confirm if your flow is running correctly?
Thanks!
Hi Sree Vani Amara
Thanks for the quick response, and thank you Anitha Abraham for creating the ticket.
I switched it to HTTP, and everything is working perfectly now.
Thank you Nuri for the update.
Please sign in to leave a comment.