# Deployment didn't put process definition in the cache
**URL:** https://forum.flowable.org/t/deployment-didnt-put-process-definition-in-the-cache/535
**Category:** Flowable Engine
**Created:** [May 5, 2017, 3:10pm UTC](https://forum.flowable.org/t/deployment-didnt-put-process-definition-in-the-cache/535 "2017-05-05T15:10:56Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@spille](https://forum.flowable.org/u/spille)
#### Post date: [May 5, 2017, 3:10pm UTC](https://forum.flowable.org/t/deployment-didnt-put-process-definition-in-the-cache/535/1 "2017-05-05T15:10:56Z")
Hi,
I’m not sure what happened, but I imported my production database into a test setup and restarted the webservice on this test server. This is something I do a lot and it never fails.
This time however, the process definition cache seems to be empty. I tried reload the cache ( PUT repository/process-definitions/{processDefinitionId} ) but I keep getting this error: org.activiti.rest.exception.ExceptionHandlerAdvice - Unhandled exception
org.activiti.engine.ActivitiException: deployment ‘123’ didn’t put process definition ‘456’ in the cache
Versions are all the same, there is nothing unusual in the startup logs,… so i’m not sure what went different this time.
Anyone else had this problem? Can I reactivate them with a rest call?
Thanks!
Cheers,
Yannick
---
### Author:  [@spille](https://forum.flowable.org/u/spille)
#### Post date: [May 8, 2017, 12:58pm UTC](https://forum.flowable.org/t/deployment-didnt-put-process-definition-in-the-cache/535/2 "2017-05-08T12:58:14Z")
I know what went wrong… We did not delete the database, we just emptied the entries but all tables etc were still there. Apparently if you do this and import the other database you get the error: “deployment didn’t put process definition in the cache”
So no biggie, just make sure you start over fresh when you even encouter this after a database import 😉