Fusion - How to know if an execution of a scenario is a RETRY or not | Community
Skip to main content
Level 3
July 10, 2025
Solved

Fusion - How to know if an execution of a scenario is a RETRY or not

  • July 10, 2025
  • 1 reply
  • 409 views

Whenever we have an error, we call a webhook to store the error in Workfront, so we can track the errors. 

However, if we use the retry error handler, we get duplicate errors. We would like to identify these duplicates and ignore them. 

The execution ID increments, so we can't use that value to see if an error is a duplicate. We don't know of any other ID variable to tie these executions together.

 

We need some way to know if an execution is a RETRY of a previous execution.

 

Any ideas welcome!

 

Best answer by Sven-iX

Hi @robertdy 
Short answer: No there's no way to catch if an attempt is a retry; the scenario state is saved, and then re-run from that point.

 

In your case you'd need to roll your own "retry" - Doable but it means you're not really storing an incomplete execution, but creating a loop with a sleep module.

 

How about this:  Before you send the event, query the issue you recorded and if found decide what to do. E.g. in your issue, record the execution ID and error type; before recording it do a search for issues with that execution ID and error type and check the entryDate vs {{now}} - if it's the BREAK modules timeout +- then it's a retry. 

1 reply

Sven-iX
Community Advisor
Sven-iXCommunity AdvisorAccepted solution
Community Advisor
July 12, 2025

Hi @robertdy 
Short answer: No there's no way to catch if an attempt is a retry; the scenario state is saved, and then re-run from that point.

 

In your case you'd need to roll your own "retry" - Doable but it means you're not really storing an incomplete execution, but creating a loop with a sleep module.

 

How about this:  Before you send the event, query the issue you recorded and if found decide what to do. E.g. in your issue, record the execution ID and error type; before recording it do a search for issues with that execution ID and error type and check the entryDate vs {{now}} - if it's the BREAK modules timeout +- then it's a retry. 

RobertDyAuthor
Level 3
July 16, 2025

Thanks for the reply @sven-ix 

This currently is our only workaround, making some kind of unique key ourselves to identify if the error is a duplicate. 

It would be nice if there was a nice simple way to have an "parentExecutionID" or something 🙂