Airport - Supporting WinAir/Talon integrated PowerAutomate Flows


This article discusses the PowerAutomate Flows created for the Airport to support their aircraft.
ITS has been asked to support these, so this document should be used to document any support information learned for this process

Target Audience

Solutions Specialist


Service Account:
Password: {Keepass}

Connectors and Flows need to be shared with any new users who will be supporting this flow.

Connectors and Flows  should be used and managed using the powerautomate@saultcollege account

Any Owner (Previously shared) or by using the Powerautomate@saultcollege account can do this

  1. Share all Flows and Connectors
    1. to be added at a later time...


Aircraft Priority Status Sheet Daily Report - Making Changes

Login to Power Automate

  • Go to
  • Click My Flows
  • Click Shared with me (if you are working on a Flow shared with you, but if using the Powerautomate@saultcollege account, then you would use Flows.

Click the Aircraft Priority Status Sheet Daily Report

In the menu bar, click Edit

You will now see the entire flow

Updating the Recurrence of the daily report

Click the first entry - Reocurrence

From here you can set the Interval and Frequency and Advance Options

Advanced Options

You can change these setting as needed.

Updating users that receive the daily report

NOTE: to do these steps you will need to have been assign permissions to the necessary flow

Click the last entry - Send an email (V2)

Enter or remove email addresses in the To field

Make sure to click SAVE when done

Adding new planes to the system

Access the Microsoft list that supports the report

Click AC_Setup in the left pane, this will open the Microsoft List

Make sure:

  1. Don't touch this documents unless requested by AirCraft Maintenance Engineer or Manager at the airport
  2. The Aircraft has been added to the Talon system first, and all fields have been populated in that system (Aircraft Maintenance Engineer's (AME) responsibility)
  3. Get up-to-date information to add to these fields
    1. Make sure to get the most up to date information for the planes from the AME, that is the same as Talon.  The data must be accurate, before signing off on an update.
    2. If the data isn't accurate the Power Automate scripts will produce errors.
    3. Data between Talon and this SharePoint (ac_setup) list has to be exactly the same.  Any deviation causes errors. 

Example of the format we need to request before making any changes:

Aircraft: ####
Priority: #
Last Run: {date}
Days not run: #
Total airtime: ####.#
Next due: ####.#
next cal due: {date in the format of yyyy-mm-dd}
WA Hours: ####.# (Same as Total airtime}
Model: ####

Testing new planes additions

Login to with the PowerAutomate Account (

Re-Run all Flow or wait for the scheduled time. Uploaded Image (Thumbnail)

If the Aircraft Priority Status Sheet Daily Report runs, then an email will be sent to those configured to receive the emails.  This can be modified as needed in the Aircraft Priority Status Sheet Daily Report script.

NOTE: To add yourself, see Updating users that receive the daily report instructions above

Microsoft Licensing

In order to use the 3rd part Flow Connectors, such as Talon and Winair a Premium Power Automate licenses has be be maintained and applied to the account running the Flows.

Microsoft started to enforce Premium Licenses for 3rd Party connectors and we never received a notification around on Feb 23, 2023

Account to apply the license to -
License that needs to be purchased/maintained on a yearly renewal - PowerAutomateplanEDU ShrdSvr ALNG SubsVL MVL PerUsr
NOTE: This license needs to be purchased yearly as we can also use the for any ITS related activities.

As of 2023 we have 3 of these Licenses Purchased.



April 2023
The SessionID from Talon rolled from 6 digits to 7 digits.  The PowerShell Flow isn't smart enough to know this.  

SOLUTION: Include the extra digit so it allows the FLOW to pull the report being requested.

Uploaded Image (Thumbnail)Power Automate goes to Talon and retrieves the Flight logs, then passes this data to SessionID.

Uploaded Image (Thumbnail)SessionID then goes through the data pull in search of the actual SessionID, via the below command

COMMAND: replace(substring(body('Get_talon_flight_logs'),indexOf(body('Get_talon_flight_logs'),'session1'),15),'session1=','')

  • The command, searches for 'session1' within the output of the Get_talon_flight_logs action 
  • Removes the 'session1=' prefix from the following 15 characters (if it exists). 
  • The resulting string is the output of this expression.

However, you will notice, that the Talon Flight Log (as seen below) has a 7 digit Session ID and not a six digit number.  I retrieved the 6 digit number I used for the below search from a failed run log and then I could see that one number was missing.

Uploaded Image (Thumbnail)Note:  above is a snip of the data the REPLACE command parses

So, to solve the issue we need to update the command to now pull 16 characters, which then will allow us to grab the extra digit.  

NOTE: You can also see that the number of SessionIDs appears to have rolled to 1 million recently, since it is 1,027,555 which re-enforced this observation.

The next time this problem will occur will be when the Session IDs role to 10,000,000.

NEW COMMAND: replace(substring(body('Get_talon_flight_logs'),indexOf(body('Get_talon_flight_logs'),'session1'),16),'session1=','')

Print Article


Article ID: 4969
Thu 2/9/23 10:01 AM
Fri 5/31/24 10:33 AM