[Resolved]Safety check complaints on the non-existent job.

Does ECS have some cache of systems?
I have a strange exception:

InvalidOperationException: The previously scheduled job MapGenerationSystem:GenerateMapJob writes to the NativeArray GenerateMapJob.mapTiles. You are trying to schedule a new job FlowFieldSystem:UpdateMapCache, which writes to the same NativeArray (via UpdateMapCache.Data.mapTiles). To guarantee safety, you must include MapGenerationSystem:GenerateMapJob as a dependency of the newly scheduled job.

I have added a dependency to the UpdateMapCache job but still got this error. Then I have removed scheduling of MapGenerationSystem:GenerateMapJob and I still got this error. And then I have commented out this job because I’ve moved its functionality to another job. I’m still getting this error despite this job does not exist in code (is commented out).

I have found a reason. When I am changing code in Rider files do not change in Unity. When I have reimported it it started to work properly.

Unity may not have detected a source code change, it happens sometimes. If you restart is issue still there?

If it is, need some code.

Strange thing is that it happens very often. I did not have such an issue earlier. Maybe it is related to Rider plugin.

Strange, never saw that after switching to Rider from VS.

I also had this issue maybe twice or thrice of Unity not auto compiling after a code chance with VS.

I am supprised to. I am glad I have switched to ridder and for past few months everything worked. This stage behaviour started today. Maybe something wrong with new version. Although I have noticed this issue with unity 2018.3 which I use in my main work. And also in 2019.3b8 which I use in my personal projects.