hello team,
is there a way to catch error , for example using run device function zebra network printer sometimes network is unstable and the printing process fails and the only thing we can see in the screen is an error message like rcp server error 500 something , it is possible to catch it on tulip and there fore perform some actions ?
+1 to this. A few things here:
Thanks for the feedback – this is a pain point we hear and are actively working to address.
Error catching in triggers is a known challenge today. Functions are designed to help solve this, giving you more programmatic control over trigger logic - but to be transparent, device functions won’t be supported on day one. We’re committed to closing that gap over time.
On the visibility side, we’re investing this year in surfacing trigger errors from the admin console, so your admins and super users can see what’s failing across apps on the shop floor without having to hunt for it.
In the near term, we’ll also be looking at two smaller but meaningful improvements: making error messages more operator-friendly (so frontline users aren’t staring at something like “RPC Server Error 500”), and extending Player’s debug logging to give admins the granular detail needed to troubleshoot device issues when they come up.
Appreciate you posting, this kind of feedback helps us prioritize the right work.
Best, Pete