Hi @feckinirish,

Teams are currently working on the first phase of Error handling. We will be introducing the ability for instances to go into a paused state when it encounters certain errors, to allow designers to resolve and resume the instance.
Supported errors include: the Connection is invalid, items cannot be found or already exist, “too many requests”. When this feature is released, documentation will include the exhaustive list.

This won’t yet return the error code into the workflow so designers can handle the error in the workflow, but we are exploring subsequent phases to this feature, to allow for customization and automation.

We’re targeting June for this feature - keep an eye on our release notes for the announcement.

Regards,

Kate Huynh

Hi @kate ,

Thank for the prompt reply. I look forward to testing this as it would greatly help in my workflows. 

Do you have any suggestions on workarounds that i could use in the meantime?

Kind regards,

Darren

Hi @feckinirish, 

Quickest workaround I can think of:

• Run a “Query” before hand
• Branch by condition
  • If file exists then “Get”
  • If collection is empty then "Upload file" or send a Task to someone for manual intervention

Hope this helps!

Regards,

Kate Huynh

Hi @feckinirish if these replies answered your question, please mark the best one!