Link and field cleanup on Jarvis failures
I have been experiencing frequent ghost links and ghost fields being left behind after a Jarvis. What should be less than five minutes per portal is turning into a thirty minute wait for the backend to cleanup the links and fields from many (not all) Jarvis usage. These ghost links/fields prevent reuse of the space, as though they are genuinely still live. Multiple restarts of the app have been tried and multiple agents are affected, confirming it is not limited to the client app performing the Jarvis.
0


