I believe the problem is most likely related to your device hostname.
If I am presuming correctly that the $ on the end of Fortigate-200A-MAST~$ is the actual hostname mode prompt; then the issue is that normally there would have been a space between the hostname 'Fortigate-200A-MAST' and the '$'.
Your device appears to contain a ~ which is most likely causing CatTools to determine the hostname as the full Fortigate-200A-MAST~$. CatTools then tries to check for this hostname plus various mode prompts after the 'end' command has been issued. This can be seen in the debuglog lines:
WFMDRetVal=8 Waiting for: "Fortigate-200A-MAST~$#"
WFMDRetVal=9 Waiting for: "Fortigate-200A-MAST~$ $"
WFMDRetVal=10 Waiting for: "Fortigate-200A-MAST~$ #"
If your device hostname prompt can be re-configured to use a space instead of the ~, then this should fix the issue.
If it can't, then you will need to raise a ticket with SolarWinds tech support as this will need to be added as a Customer Feature Request (as the device type script will need modification)