Hi @jatoxa ,
It looks like the messages from the UDP trigger are coming through in their raw binary form. In my test, I sent "Hello world!" to FME Server via UDP and it came through as "SGVsbG8sIHdvcmxkIQ==" I was able to 'unscramble' the message within a Workspace using the BinaryDecoder transformer. In my case, I set the Encoding Type to Base64 and the Character Encoding for Output Data to System Default to get the proper string output.
I'll check with our team here to confirm if this is expected behaviour. I also would have expected the messages to automatically be decoded when FME Server/Cloud receives them.
Hi @lauraatsafe,
Fantastic, thanks! I actually tried it but forgot to set the character encoding. All my messages makes sense now.