Audit Log for Workflow Configuration Changes

Follow

Vaibhav Jagetia

• 15 December 2025 23:26

We’ve noticed that workflows which were originally configured correctly and running as expected sometimes appear to be changed later either inadvertently or by someone else resulting in issues.

To help prevent this, is it possible to add an audit log in aXc that shows when workflow settings were updated and by whom? Having visibility of configuration changes would help us identify how or who may have accidentally changed them, so we can be more careful going forward.

5

• 

  Pip Austin

  • 15 December 2025 23:58

  I'd love to see audit logs like this so we can better identify areas where staff may need further training or where there are gaps in restrictions of access permissions. 

  Also good for showing records of continuous improvement when we intentionally implement updates.

  3

  Comment actions Permalink
• 

  Petra Leslie

  • 13 July 2026 00:26

  Very much agree, We've also noticed that workflows which were originally configured correctly and running as expected sometimes  are changed, resulting in issues.

  Visibility of configuration changes would 100% help to identify how these faults and issues occur.

  Some examples of this playing out... 

  • A saved qualification condition attached to a workflow will suddenly go missing, with no clear reason why.
  • On multiple occasions we've saved changes, navigated away, and come back to find the save didn't actually take, even though everything looked saved at the time.

  This has happened enough times now that we suspect it isn't just user error, there may be an underlying bug with how saves are being committed or persisted. Without any audit trail, we have no way to confirm what actually happened, which makes it very hard to raise with any confidence or troubleshoot properly.

  Seeing this issue makes me think that others are potentially experiencing this? Given how central workflows are to day to day operations, we'd really value some transparency here, both an audit log for changes, and confirmation from Axcelerate on whether this save issue is a known bug.

  We've also raised this directly with aX team, but it's interesting (and a bit concerning) to see this thread confirms we're not the only ones. Is this a wider problem with aXc and saving in general, or specific to workflows?

  To add some more detail, we were very sure a particular workflow was configured and working correctly, tested multiple times, then it suddenly broke with no changes made on our end. This had potential for serious repercussions, which is what's prompted us to push harder on getting some visibility into this.

  2

  Comment actions Permalink

Please sign in to leave a comment.