Sam P Posted February 6, 2024 Posted February 6, 2024 I have some workflow failures this morning, all relating to the Date Formatter (3 separate workflows so far) all with the same error, none of the workflows have been edited recently and have been working fine:
Keith Stevenson Posted February 6, 2024 Posted February 6, 2024 @Sam P Thanks for the post. This is now resolved. This was due to a Ibridge file that seems to have been corrupted on download\application to your instance this morning and resolved by replacing the file with a valid copy. We will look to add additional sanity checks to ensure that this doesnt happen again. Kind Regards Hornbill Cloud Team
Sam P Posted February 6, 2024 Author Posted February 6, 2024 @Keith Stevenson that's great, I have restarted the processes and all are progressing as expected. Thanks for your swift action.
Art at BU Posted February 7, 2024 Posted February 7, 2024 Hi @Sam P We seem to have the same or similar issue this morning. Can you advise if this is another example of the problem? We see the similar message... and the failed node is the date formatter... Thanks, Art
Art at BU Posted February 7, 2024 Posted February 7, 2024 Hi @Sam P, We have restarted the workflow and it seems to be OK now. This is good but I just wonder if there is anything you can suggest we check? Regards, Art
Keith Stevenson Posted February 7, 2024 Posted February 7, 2024 @Art at BU The issue would have effected any IBridge Nodes fired during the time of corruption (From around 5am to 10am) but as you have found restarting the BPM will resolve the issue. We have now also implemented a check that will mean we see any similar issues long before customers do in future. Kind Regards Hornbill Cloud Team 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now