Clicking Comala workflow link in document results in 400 (bad request) error

[Greg Wolff]

We have Comala workflow installed.  We can see the link to "Add workflow" etc at the top of each page in Confluence. While it used to work, it doesn't seem to be working now.

Clicking on the link results in nothing happening.  I used right-click and "open in new tab"

and got the following in the new tab

---

Type Exception Report

Message Invalid character found in the request target [/wiki/plugins/servlet/ac/com.comalatech.workflow/workflow/overview/%7Bspace.key%7D/%7Bcontent.id%7D?contentType={content.type}&contentVersion={content.version}&darkDebug={condition.feature_flag(featureKey=cwc.debug)}&page.id=xxxxxxx&space.key=DE&content.id=xxxxxxxx&content.version=2&page.type=page&page.title=Outage%20of%20Cloud%20Services&space.id=xxxxxxx&content.type=page&page.version=2 ]. The valid characters are defined in RFC 7230 and RFC 3986

Description The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

Exception

java.lang.IllegalArgumentException: Invalid character found in the request target [/wiki/plugins/servlet/ac/com.comalatech.workflow/workflow/overview/%7Bspace.key%7D/%7Bcontent.id%7D?contentType={content.type}&contentVersion={content.version}&darkDebug={condition.feature_flag(featureKey=cwc.debug)}&page.id=xxxxxxx&space.key=DE&content.id=xxxxxxxx&content.version=2&page.type=page&page.title=Outage%20of%20Cloud%20Services&space.id=xxxxxxx&content.type=page&page.version=2 ]. The valid characters are defined in RFC 7230 and RFC 3986
	org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:494)
	org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:271)
	org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
	org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:890)
	org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1743)
	org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
	org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
	org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
	org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	java.base/java.lang.Thread.run(Thread.java:829)

Note The full stack trace of the root cause is available in the server logs.

[James Conway]

Hello @Greg Wolff 

Could you share the full stack trace and reproduction steps with our Customer Success team via https://support.comalatech.com

Thanks in advance

James