# This is a Bug Report
Description
I've created a Lambda using the following template: aws-kotlin-jvm-maven, printing an hello world inside the handler as a log.
Next i've added
events:
- schedule: rate(2 minutes)
just under the handler, in functions->hello, in serverless.yml.
Next I've deployed my lambda using serverless deploy.
Looking at logs, i came through something like this:
After first run:
0 [main] INFO com. example.Handler - Hello, World! com.example.Handler@551aa95
After second run:
119497 [main] INFO com. example.Handler - Hello, World! com.example.Handler@551aa95a
119497 [main] INFO com. example.Handler - Hello, World! com.example.Handler@551aa95a
After third run, another log has been added. And after any run, another is added. It looks like it doesn't "destroy" old ScheduledEvents. Same problem occur with the java template.
I've tried a node template, with the same Serverless config, and this is not happening.
I'm using Serverless v 1.24.1
# This is a Bug Report
Description
I've created a Lambda using the following template: aws-kotlin-jvm-maven, printing an hello world inside the handler as a log.
Next i've added
just under the handler, in functions->hello, in serverless.yml.
Next I've deployed my lambda using
serverless deploy.Looking at logs, i came through something like this:
After first run:
0 [main] INFO com. example.Handler - Hello, World! com.example.Handler@551aa95After second run:
After third run, another log has been added. And after any run, another is added. It looks like it doesn't "destroy" old ScheduledEvents. Same problem occur with the java template.
I've tried a node template, with the same Serverless config, and this is not happening.
I'm using Serverless v 1.24.1