There is an edge case where Fission thinks it has specialized the workflow environment to the workflow, even though the Fission Workflow engine did not persist the workflow (because of an error).
The current workaround is to delete and re-create the Fission Function.
Fixes needed
[ ] Add support to Fission to invalidate a specialization on a specific HTTP response.
[ ] In the Fission Environment proxy ensure that specialization fails in case of workflow errors.
There is an edge case where Fission thinks it has specialized the workflow environment to the workflow, even though the Fission Workflow engine did not persist the workflow (because of an error).
The current workaround is to delete and re-create the Fission Function.
Fixes needed