Workfront Fusion

RobertDy · 7/10/25

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!

Sven-iX · 7/12/25

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.

View solution in original post

Sven-iX · 7/12/25

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.