Hi everyone, I'm excited to be trying out the new Fission bot support on Azure, but I've run into an issue in my dev environment. I'm hoping someone can help me determine if it's a configuration problem. While Medplum and Fission seem to be working, I get an exception when I click 'Run' in the bot editor. The bot saves to Azure Blob Storage and deploys to Fission correctly. I can execute the bot manually via the Fission CLI and direct HTTP requests. However, running it from the editor page fails. The Medplum logs show an excemption: 'TypeError: this.readable.on is not a function', which is thrown by AzureBlobStorage.writeFile. I suspect this is triggered by the writeBotInputToStorage function in the Medplum server. This seems like a storage configuration issue, but I'm not sure why Medplum can write the bot's code to storage but not the bot's input. I'm planning to debug the server locally, but I wanted to check if anyone has seen this before. Any help would be much appreciated! Thanks, Dougie

@dougie , thanks for the report here. Our support for fission is bleeding edge at the moment. I'll file a issue for this and we'll investigate.

Thanks @Ian Plunkett I'll debug through the code today to see if I can work out what's going wrong. I'm happy to raise an issue on GitHub if I think that a change in the Medplum server would fix it (I wouldn't be surprised if I've just got a config problem somewhere).