Quote:
Also has to do with float vacation needing to be processed manually and it pauses the entire system when the person requesting a float drop is next in the que. Then a scheduler gets to it when they get to it. Until that happens everything is frozen. A couple years ago they were supposedly dedicating a scheduler to be sitting there just processing float requests but we don’t have a way to hold them accountable and I’m sure they aren’t doing it.
Originally Posted by Qotsaautopilot
I could be way off but I think it’s about the amount of processing power Spirit chooses to buy from Sabre and we don’t have anything contractually requiring them to make it any faster.Also has to do with float vacation needing to be processed manually and it pauses the entire system when the person requesting a float drop is next in the que. Then a scheduler gets to it when they get to it. Until that happens everything is frozen. A couple years ago they were supposedly dedicating a scheduler to be sitting there just processing float requests but we don’t have a way to hold them accountable and I’m sure they aren’t doing it.
That might be what’s *supposed* to happen for float (or mandatory float). But pretty sure that’s not what actually happens. I put in for mandatory float right at noon on Thursday. It didn’t process it until about 3am and I could watch the days I wanted change red to green and vice versa, which in theory shouldn’t have happened if it shuts the system down until someone approves it.
Sent from my iPhone using Tapatalk