I’m experimenting with Nextworld’s AI tools in an environment that doesn’t have a Tenant Default Lifecycle. I created a branch lifecycle and used Project Builder to agentically create a feature. After that was done, I created an Embedding Definition in the same branch lifecycle over one of the tables that was created agentically. After that was done I ran the Synchronize Embeddings form action, and got this message:
Warning - Embedding Synchronization always runs in the Tenant Default Lifecycle, against the embedding configuration that exists within the Tenant Default Lifecycle Even if the embedding configuration exists in the current lifecycle, the synchronization will retrieve the Tenant Default Lifecycle version.
The two jobs that got spun up both failed with System error - could not find table nsPTestEquipmentInventory
I believe understand the message and assume the job errors are because the table I created the embedding over is only inside a Branch Lifecycle. The question I have is why is it implemented this way and why don’t I get an immediate error rather than 2 failed background tasks?
