Deployment issue with EventBridge?


I’ve been using serverless’ support for EventBridge extensively for some time now (right now I’m on 1.60.0), and for the most part it has been very well in my architecture. However, I’m occasionally having problems with an apparent deployment issue.

Once in a while, when I change the event rule pattern for a Lambda and redeploy my stack, the CloudWatch Events trigger isn’t updated but actually removed. I still see the custom resource which supports EventBridge in the CloudFormation stack, but no matter how many times I try it won’t add the trigger back to the Lambda function. I wind up undeploying and redeploying the stack, which is distressing because for example I lose history on Step Function executions.

Is this a known issue? If so is there a fix in the works, or some way to work around it?

1 Like