In response to Andy Buck’s original post.
I posted this response in reply to Andy’s official bug report. I am repeating that response here to alert community members that the problem may be resolved.
I was able to reproduce the ‘(400) Bad Request’ error by clicking the “Send” button for a ‘FileSave’ workflow action that did not create any file content. No file content is present for any workflow rule for which the workflow rule ‘Condition’ is false.
I cannot be absolutely certain that this is the error that you are seeing because the screen shot does not indicate which “Send” button you clicked. However it is very likely that this is the source of the problem.
I have updated the software to report a meaningful error when the “Send” button is clicked when no file content is present. This new error message reports that no file was saved because no file content is present. The error message suggests checking whether the workflow rule ‘Condition’ is false.
If testing goes well, this change will be released on Friday afternoon 1/17/2020.
Please try repeating your tests once the change is released.
In the interim you can verify whether this is the source of the problem.
- Try clicking the “Send” button for any workflow actions where the ‘Condition’ is true. This should save the file.
- Try clicking the “Send” button for any workflow actions where the ‘Condition’ is false. This should yield the ‘(400) Bad Request’ error.
Please let me know what your testing reveals.