Unanswered

Pager Duty Output

(0) Share

Report

Posted on by Community Power Pla...

Hi,

So i ran into a wierd issue that actually stopped my flow from working, I was actually creating an incident in Pager Duty and then getting the details of that particular incident using "Get Incident" connector of pager duty, The output of get incident connector gives me the "No." of that incident which got created in Pager Duty. But suddenly from today i'm just getting the Headers in the output and no body?

I re-checked my original succesfull runs and saw that there was 1 retry everytime in Get Incident step. ( probably because API needs some time to create the incident ) .

Can someone help me why the connector is not retrying?? I've provided the screenshot of both outputs below :

retryingnot retrying

Categories:

General topics

I have the same question (0)

All responses (2)

Answers (0)

v-bacao-msft on at

Like (0)

Report

Hi @Anonymous ,

Could you still reproduce your issue now?

I tested it on my side, and the output of Get incident did not contain the expected Body.

I found that the incident created using Create incident action did not appear in the Incidents list in PagerDuty portal.

If you manually create an incident in PagerDuty and copy the Incident key to Get incident action, the Body will appear.

It seems that the incidents created using Create incident are invalid.

Best Regards,

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Hi @v-bacao-msft ,

Yes I can reproduce the incident and its still failing when the incident gets created by Create incident step,

It seems to me that the "Get Incident" step was previously "retrying" ( as you can see in the 1st picture of my question)
during the 1st try it might not getting the correct output and thus retrying but now it stopped retryng ( as you can see in the 2nd pic )
if i pass that incident key separately or after some delay of like 10-15 sec it'll work ( i assume, i'll try that )

Is there some settings that actually allows us to set that whether or not we want to retry that step???

you can see that in the retry part it was previously getting "Internal server Error:
"

Was this reply helpful? Yes No