08-19-2023, 10:00 PM
After analyzing the issue, it seems that the problem was with a state variable (from the A2A tablet) being saved incorrectly in your specific saved flight. By using the correct A2A tablet JS file and setting the variable correctly, then re-saving the flight, you have been able to resolve the issue.