Hi,
I’ve recently been experiencing issues with two of my workflows. They are very simple — just three steps: a trigger, a Python code step, and a ChatOps Slack action. The problem is that the ChatOps action takes a long time to execute and eventually fails with the following error: job step input "message" already exists for step 1e3e3e72-a61e-4f2f-b052-03306c3a1b98 in job bc5d62d3-9e9d-43cc-89d4-675739c8e50a, please reference this request ID when contacting support: d779f308-90be-460f-9ead-a1adcfa35d7d
In one workflow, I originally had three ChatOps steps. I tried adding sleep steps between them, and I even split them into separate workflows. That worked for a bit, but the error came back. I also tested different trigger types in case the trigger was contributing to the issue, but the problem persisted.
What I find confusing is that I use this same ChatOps action in other workflows without any issues. I’m not sure how the Python step could cause this error, especially since I don’t have any variable named message anywhere in the workflow. The Python step outputs a variable called result, and the Slack ChatOps step uses the default message input, which can’t be renamed.
Any help or guidance would be greatly appreciated.
Thanks!