Skip to main content
October 26, 2023
Solved

Integration Calling Twice on 404 with Connected System

  • October 26, 2023
  • 4 replies
  • 0 views

Hi,

I have a set of Integration object that uses a Connection System (OAuth2: Client Credential Grant).
I am testing direct on the Integration object with blank attributes:
1. If it use connected system and the API returns 404 (i.e. user not found), the API will always fired twice (not expected). Below are the debug logs:
2. If it use connected system and the API returns 200, the API will only fired once (expected). 
3. if I remove the connected system and the API returns 404, then it will only fired once (expected). 

2023-10-26 07:26:14,981 - {
  "origin" : "local",
  "type" : "request",
  "correlation" : "d782eed85047a462",
  "protocol" : "HTTP/1.1",
  "remote" : "localhost",
  "method" : "POST",
  "uri" : "https://example.com/path/to/service/07?test=001",
  "host" : "example.com",
  "path" : "/path/to/service/07",
  "scheme" : "https",
  "port" : null,
  "headers" : {
    "Authorization" : [ "XXX" ],
    "Content-Type" : [ "text/plain; charset=UTF-8" ]
  },
  "body" : "[id:1234]"
}
2023-10-26 07:26:15,532 - {
  "origin" : "remote",
  "type" : "response",
  "correlation" : "d782eed85047a462",
  "duration" : 553,
  "protocol" : "HTTP/1.1",
  "status" : 404,
  "headers" : {
    "Cache-Control" : [ "max-age=604800" ],
    "Content-Length" : [ "433" ],
    "Content-Type" : [ "text/html; charset=UTF-8" ],
    "Date" : [ "Thu, 26 Oct 2023 07:26:15 GMT" ],
    "Expires" : [ "Thu, 02 Nov 2023 07:26:15 GMT" ],
    "Server" : [ "EOS (vny/0453)" ]
  },
  "body" : "\n\n\n\t\n\t\t404 - Not Found\n\t\n\t\n\t\t

404 - Not Found

\n\t\t\n\t\n\n" } 2023-10-26 07:26:15,900 - { "origin" : "local", "type" : "request", "correlation" : "a1dcea355e1fa8a5", "protocol" : "HTTP/1.1", "remote" : "localhost", "method" : "POST", "uri" : "https://example.com/path/to/service/07?test=001", "host" : "example.com", "path" : "/path/to/service/07", "scheme" : "https", "port" : null, "headers" : { "Authorization" : [ "XXX" ], "Content-Type" : [ "text/plain; charset=UTF-8" ] }, "body" : "[id:1234]" } 2023-10-26 07:26:16,450 - { "origin" : "remote", "type" : "response", "correlation" : "a1dcea355e1fa8a5", "duration" : 549, "protocol" : "HTTP/1.1", "status" : 404, "headers" : { "Cache-Control" : [ "max-age=604800" ], "Content-Length" : [ "433" ], "Content-Type" : [ "text/html; charset=UTF-8" ], "Date" : [ "Thu, 26 Oct 2023 07:26:16 GMT" ], "Expires" : [ "Thu, 02 Nov 2023 07:26:16 GMT" ], "Server" : [ "EOS (vny/0453)" ] }, "body" : "\n\n\n\t\n\t\t404 - Not Found\n\t\n\t\n\t\t

404 - Not Found

\n\t\t\n\t\n\n" }



Is this an Appian bug, and do we have any workaround for this?

    Best answer by stefanhelzle0001

    Calling the API two times might be because Appian gets a 404, then tries to talk to the oAuth service, then tries a second time.

    4 replies

    stefanhelzle0001
    October 26, 2023

    Calling the API two times might be because Appian gets a 404, then tries to talk to the oAuth service, then tries a second time.

    October 27, 2023

    Thanks for answering, if this is the reason, is there anything we can do. Shouldn't it the be 401 instead for the logic to retry?

    The issue with this is on logging side we will always log twice, hence causing false alarm on the error occurrence rate. 

    stefanhelzle0001
    October 27, 2023

    I think there is nothing you can do. If this is a real issue, I suggest to open a support case.