It's pretty long to explain, but I have opened a ticket (CS1253174) about a space where intermittently a source was losing parts of its grain - specifically, dimensions imported from another space through a package. Support mentioned a flag called "Disable Implied Grains Processing", which is only visible from the backend, not by users; they set it to true. Apparently, when this flag is false Birst may modify grains on its own for some "automatic" data analysis which I honestly did not understand. Also, Support gave me an advice about my workflow: I was publishing the parent and the child space in parallel, but only for sources which do not depend on packages; they suggested to split all steps in the workflow to avoid parallel tasks.
So my questions: is this really an expected behavior? Why exactly was Birst removing the imported dimensions from the grain? What is the point of having the possibility of parallel tasks in workflows, if then such weird behavior may happen? Why are such flags hidden from end users? Troubleshooting things like this with "blind eyes" is really tough.
