Closed jgranduel closed 7 years ago
Hi,
There seems to be something wrong with your BPMN diagram. Could it be that a sequence flow isn't connected? Could you provide the app that you're trying to deploy?
We'll have a look at making the error message more descriptive.
Regards,
Yvo
I managed to download the app as a zip.
Hi,
After you said "Could it be that a sequence flow isn't connected?" I double checked connections. And indeed the sequence flow from start event was missing (the "gigplan.png" thumbnail shows it's missing). But it was present in the designer! so might be a refresh issue??
Sorry for wasting your precious time...
Hi,
I noticed that too after importing the app. I'll investigate it.
Regards,
Yvo
After correcting the missing / not connected sequence flow the model was deployed successful. We'll add a check to the validator to prevent this. We'll also investigate improving the feedback on what caused the deployment to fail.
Regards,
Yvo
I ran into the same issue just now with the same tutorial. Let me check the BPMN diagram. I assume it is the same root cause. Yes, the "Invalid deploy result HTTP 1.1/500" error does not help me
Ok, I did not notice the validation checkmark until now. However, when I clicked it, I got a bunch of errors. It says "Invalid source for sequenceflow". But it does not tell which of sequence flow is wrong. It will be useful if double clicking on the error will take me to the exact flow line on the diagram.
Hi,
There seems to be something wrong with your BPMN diagram. Could it be that a sequence flow isn't connected? Could you provide the app that you're trying to deploy?
We'll have a look at making the error message more descriptive.
Regards,
Yvo
Thank you. I faced the same but after correcting the flow sequence connection, process got published. Flowable version 6.6.0
Hi,
I'm following Paul HH's introduction "Instant Gratification with Flowable 6".
Env: Win10 x64
A the publish moment, I get an "Invalid deploy result code: HTTP/1.1 500". I might have make an error in typing or somewhere else but still!
Here's stack trace:
Hope this is enough to be useful. Best regards