My Perspective project disappeared from the Gateway I don't know why. It is visible in the designer but it disappeared from the project browser in the Gateway (so I cannot run this project as a client). I can see the project in System>Projects but not in Perspective>Launch.
Restoring the whole project from a backup helps but after some time it disappears again.
There is nothing suspicious in the Gateway logs.
There was a topic on this forum about project disappearing from Designer Project Browser but the solutions there did not help me much.
We'll need more information in order to diagnose what's going on here.
Which Ignition edition (standard, edge, maker)?
Is this the only project on the Gateway?
Does the project have Perspective content (Views)? If a project has no Perspective content to launch to, it won't show as a launchable Perspective project.
Is there a page configuration in place which includes exactly one entry that has a URL of /? Other page listings are fine, but a page listing with just / is required to operate as the "home" page of the project.
Is the project configured to be inheritable? Inheritable projects are not directly runnable; their "children" are the runnable projects.
No, there is another one but I don't use it (it is not empty)
Yes
Yes, it has
It is not inheritable
Someone has upgraded the gateway from 8.3.0 to 8.3.7 (I guess) and every Alarm Status Table after the upgrade disappeared, so I uninstalled it and I installed 8.3.0 again. Everything was fine but since that moment the project started disappearing. After installing 8.3.0 again I used the Gateway backup 8.3.0 so in my opinion nothing should collide. I don't know if the version changes are the cause or it is just a coincidence but I think it is a good idea to mention it.
They very well could be, but it depends on what was changed. If you had an 8.3.0 project with Perspective content, then upgraded to 8.3.7, and that update either modified existing content to have a new shape, or new content was added with a shape unique to some version later than 8.3.0, then rolling back to 8.3.0 could potentially result in that content being un-serializable in 8.3.0.
Example:
Suppose 8.3.2 added a new prop named discoverable to the Alarm Status Table. Your upgrade to 8.3.7 would include those changes to the component structure. Rolling back to 8.3.0 is now asking your 8.3.0 Gateway with no concept of that field to parse the component.
You're going to need to reach out to Support for verification - this isn't something I would be able to diagnose well through forum posts.
This really sounds to me like you've maybe got some weird thing happening on your filesystem, or someone's mucking around with git, or something else like that. An upgrade is not going to spontaneously remove one type of component and leave the rest of your views unchanged; there's simply no mechanism to do that kind of thing.
Usually, it happens after restoring the whole Gateway or restoring this certain project. I work on two servers; one is the main server for our client and there is a small one (on a laptop) for me to work on it (both are connected to the PLC). After I do some changes on our local server I transfer the whole Gateway backup or just project to the main server
