Skip to main content

Hello!

 

We want to start a process flow (see image below - process flow A) with an API trigger.

Process flow A

 

For triggering it, we used another process flow with a web connection and a simple table task to start the process (see image below - process flow 😎.
 

Process flow B

 

We have managed to make it work in Postman, giving us an OK 200 status. However, in the universal gui, the flow exits with a -1 error code (see image below for the live error log). Both authentication methods are exactly the same between our web connection and Postman.

 

 

Any ideas about what we might be missing?

Is there a resolution for this topic? I need to start a base model process flow with an api trigger. 
Is there another solution to start a process from a base model?

Hello @Valentin,

Apologies for the late reaction to this topic.

Judging by the error message “No such host is known”, it appears that the URL is invalid or refers to a host name (domain) that is unknown/unreachable. Can you share the configuration of the Web Connection and the Endpoint that are referenced by the process action? I’m interested in the Base URL and Path in particular.

@Ionut_Catalin There is no other way to start a process flow of a base model other than an API call at this moment. For an API call, your options are a Web Connection or an HTTP Connector, both from a process flow. Valentin’s example in this topic should work just fine once we figure out what’s wrong.

Hi @Valentin,

It seems you are calling Indicium itself with the WebConnector correct?

I understand you used Postman to validate your request and it works, but because you probably executed it from your computer, it might work a bit different due to DNS/Network configuration.

Your computer might be able to resolve the DNS hostname and able to connect to it - but the server might not be able to connect to itself.

If you open a remote desktop to your server and open a browser, can you validate that the URL you used in the webconnection works from your browser?

I suspect that it won’t work and if that is the case, you can cheat by adding a line on the server that is not working to this file: C:\windows\system32\drivers\etc\hosts. If you add 127.0.0.1 dvdb-dev.thinkwise.com it probably starts working. (replace dvdb-dev.thinkwise.com with your hostname).

But I do recommend setting up some internal DNS record on your DNS server. You should probably ask someone from your IT infra department.

​Hi @Dick van den Brink  and @Vincent Doppenberg . 
We discovered if instead of DNS we put the IP address and add to the Headers the parameters "Host” with the corresponding host it is working also in our application. 
For now, we are not sure why with this combination works and with DNS directly not. For now we indeed contacted someone to have a better look over the DNS part and we'll keep you updated.

If you have any other ideas we're open to them, we will look also into your suggestion with remote desktop.

Reply


Terms & ConditionsCookie settings