After every Moqui docker build reindex required for task show in WorkManagement

Hi Everyone,
I need your help with this issue regarding every new Moqui docker build task that isn’t visible until manually reindexing.
Regarding my setup detail’s:-

  1. I am running the Moqui docker container and OpenSearch through docker-compose.
  2. My database is cloud-managed Postgres.
  3. Application based on HiveMind (GitHub - xolvegroup/WorkManagement).

If any further details are needed for this issue please let me know.
How can I solve this issue without every time need not reindexing required for all the tasks visible in WorkManagement?
Demo setup.
https://demo.xolvegroup.com/Login#login
Thank you everyone! Have a good day

1 Like

How are you building your docker image, and what is a task. Do you mean ServiceJobs should be run automatically on startup or data should not be loaded automatically?

@michael We do not face any issues with manual indexing. Our main problem is that we do not want manual indexing whenever we build a new docker image. Tasks should load automatically. Any other information you needed please let me know. Thanks for your response.

1 Like

How do you build your docker image? What do you mean by a task?

@michael my docker build steps are below:-


Tasks mean every ticket assigned to anyone. for reference the image

It looks like you’re running with OpenSearch embedded (given the downloadOpenSearch gradle task that is run), and unless you have its data directory inside the docker container mapped to a directory on the docker host filesystem, or in some other way preserve that data between container destroy/create, then you will have that issue.

This assumes one thing you didn’t mention, which is necessary to mention for custom code like this (in your Work Management application). To cover bases it can be helpful to include a link to the screen or other code involved, when it is available publicly anyway (which I believe this app from Xolve is, ie made available under the xolvegroup on github). The important point in this case is where does that screen get its data? Is is from the relational database or from opensearch? Based on the behavior you are describing my guess would be from opensearch, but that is another guess…

1 Like

Thanks @jonesde I will check and update as you have suggested.

1 Like