You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when subject is changed and switch to report view, subject definition might be changed already, and since subject saving is automatically and frequently, subject data might still not submit to server side. which will cause report data fetch failed (server side error, typically).
and in this case, an unmount monitor for saving queue is added, it will submit the changed data to server side immediately when route changed. but it still cannot avoid above exception.
seems have to wait for saving response when switch route between connected space, subject and report.
dashboard and pipeline graphics share the same mechanism, since they have no route switch issue, works better now.
The text was updated successfully, but these errors were encountered:
when subject is changed and switch to report view, subject definition might be changed already, and since subject saving is automatically and frequently, subject data might still not submit to server side. which will cause report data fetch failed (server side error, typically).
and in this case, an unmount monitor for saving queue is added, it will submit the changed data to server side immediately when route changed. but it still cannot avoid above exception.
seems have to wait for saving response when switch route between connected space, subject and report.
dashboard and pipeline graphics share the same mechanism, since they have no route switch issue, works better now.
The text was updated successfully, but these errors were encountered: