This issue has been resolved and Workflow is now functioning as expected. We have identified a longer term solution to prevent this from occurring in the future.
·
