Error Message

Service files not changed. Skipping deployment…


On each deployment, Serverless Framework checks if your Lambda code and config have changed by computing the SHA checksum and comparing it to the previous deployment. If unchanged, Serverless skips the deployment.

This can be undesirable if your previous deployment failed due to an external factor that has nothing to do with your code.


Serverless Framework has an option to skip this check and deploy anyway. Use the --force flag when you run serverless deploy.

$ serverless deploy --stage dev --force