topic Re: Problems debugging WebEx connect flows in Webex Connect

Problems debugging WebEx connect flows

dorel-barbu — Mon, 09 Oct 2023 13:11:27 GMT

Hello,

I have been trying to build a simple flow that sends an SMS to a particular phone number after a custom event has been posted via the API. Upon using Postman to send the request I am getting back a response:

{ "notifyurl": "", "events": [ { "evtid": 6751, "correlationid": "ABC123", "parameters": { "message": "hello world" } } ] }

However, I am not able to view any debug logs in the flow sections.

I have seen the following message but I am not sure what it means. To generate logs, invoke this flow by attaching it to the rule in this session. - How is this achieved exactly?

Also, I tried to navigate to the debug console and search the logs by transaction id, or by anything that was available and I am not getting back anything.

Can somebody assist me in resolving this issue, please?

Thanks in advance!

Re: Problems debugging WebEx connect flows

Connect - Tanuj — Tue, 10 Oct 2023 03:38:58 GMT

Hi @dorel-barbu - Were you able to publish the flow successfully? It sounds like your flow isn't getting triggered at all due to which there aren't any debug logs in the console.

If you're using an inbound webhook to trigger the flow, a simple Start Node configuration could look like below:

To trigger the flow you would need to use the Webhook URL that's gets generated in your local system.

Please can you share more info about your configurations and the response you are getting on invoking the Webhook/Custom Event API to help further investigate the issue you're facing.

Re: Problems debugging WebEx connect flows

dorel-barbu — Tue, 10 Oct 2023 08:16:18 GMT

Hello @Connect - Tanuj , thanks for getting back to me!

I have configured the flow to be triggered upon sending a custom event. Here's how it looks like:

Then I have called thee following API

https://api-sandbox.imiconnect.io/resources/v1/events/externalevent/

WIth the following payload:

{ "notifyurl": "", "events": [ { "evtid": 6751, "correlationid": "ABC123", "parameters": { "message": "hello world" } } ] }

I have received the following response:

{ "response": [ { "code": "1002", "description": "Queued", "transid": "6acf9f90-c6b0-434e-a704-16b19921360c", "correlationid": "ABC123" } ] }

1. Have I configured something incorrectly here? I was expecting the flow to be triggered after the custom event was received

2. Do I need to trigger it using an inbound webhook?

Re: Problems debugging WebEx connect flows

mparra.fusionet — Tue, 10 Oct 2023 18:26:36 GMT

Hi @dorel-barbu,

I have working exactly what you have with a custom event also, I didn't go the route of inbound webhooks as @Connect - Tanuj suggested, I can't recall why, but it must have been due to some flexibility I found on it vs inbound weebhooks.

As @Connect - Tanuj said, can you please send the complete screenshot configuration of the Custom Event (Assets> Integrations > Click Manage in the TestEvent) and the Event Node in the flow, the previous screenshots weren't showing all of the text in the Event Node.

Since we don't have screenshots of the Flow, make sure it is enabled:

Since Webex Connect is responding with a 200OK with that response, at least we know it made it there, to peek a bit more under the hood, use the transaction id you got as a response and go to:

Debug > Debug > Query by Transaction ID:

Here, paste the transaction ID you got from the WebexConnect Cloud (below) and see what you get:

6acf9f90-c6b0-434e-a704-16b19921360c

This should give you the full visibility to tell if the Flow you is really getting invoked, You can tell that there are "Rules" I can't see on my sandbox tenant, which that really trigger the custom event, hopefully this will help you.

If all looks good even in the log (right flow, right custom event ID - 6751), create a new custom event, a new flow and try again ( the software equivalent of reboot on hardware).

Re: Problems debugging WebEx connect flows

dorel-barbu — Wed, 11 Oct 2023 10:50:50 GMT

Hi @mparra.fusionet ,

Thanks for getting back to me!

So, taking the transaction id and putting it into the debug console, doesn't yield any results.

Here is a screenshot of the flow, I can see that the number of executions is 0, which is a bit weird:

And this is a screenshot from the event configuration:

I have recreated the flow triggered by a custom event multiple times, with no success.

However, it seems that I am able to trigger a flow using a webhook.

Let me know if you have other suggestions!

Thanks again,

Dorel

Re: Problems debugging WebEx connect flows

mparra.fusionet — Tue, 17 Oct 2023 05:03:42 GMT

Hi @dorel-barbu

Thank you for the screenshots, in my eyes your configuration and even the response you get from Webex Connect is good, it looks like a software issue where you can't really do much but opening an support case, specially because your debug console doesn't show anything and webhooks work.

Since I can tell that you are using - just like I am - the sandbox I don't think there is any support besides this forum, let me turn it to the only Cisco person I know:

@Connect - Tanuj is there any way to have @dorel-barbu's issue looked at under the hood? We have the transaction ID and I am sure that dorel can give you his tenant username privately over community messages, in short it seems that the Webex connect Cloud does respond perfectly but Webex Connect is not processing the request.

Re: Problems debugging WebEx connect flows

Connect - Tanuj — Tue, 17 Oct 2023 22:33:32 GMT

Hi @mparra.fusionet - This has been raised to the backend team. Will get back as soon as we have an update.

Re: Problems debugging WebEx connect flows

dorel-barbu — Wed, 18 Oct 2023 10:17:40 GMT

Amazing, thank you very much for checking this!

Re: Problems debugging WebEx connect flows

Connect - Tanuj — Fri, 27 Oct 2023 14:47:16 GMT

@dorel-barbu - A one-off backend issue caused the problem that you faced. It was limited to that specific flow and it's been addressed now. Please try to invoke the flow now using Custom Event API. It should work. Let us know if you face any issue.