It would be nice to have an event log like in windows. (doesn’t have to be all flashy, just a read-only tulip table will be more than enough.)
Every time there is a Tulip error message an entry is made in the event log with station name, App name, step name, user, date and time, error message, etc.
This should also capture events when we use the “show error” trigger function.
This will be very similar to the completions table, but for errors.
The alternate method I can think of is for us to have step trigger for “ON STEP ERROR” then we can decide what to do with it. (We can write to our own Tulip table)
This will be a great tool for developers to diagnose apps.
This in conjunction with station “live preview” would make managing multiple stations so much easier.
below is a screen capture of the windows log I’m referring to.
This is a fantastic idea (or couple ideas). I wrote up a feature request for this functionality. As a user I have found myself wanting similar functionality in the past. Is there other information (outside of errors) that you would like to see? I could see a few being useful:
When triggers executed
When errors occurred, and debugging information
Maybe a special type of console logging message that isn’t shown to users
Anything else?
There is a lot of work going on around the tools we offer to help engineers manage their Tulip deployments at scale, so your thoughts would be incredibly valuable here.
error log and when triggers are executed will be the top 2 in my wish list.
I guess some diagnostics for connectors but I haven’t used connectors to comment on it. I will keep thinking…
Another that is coming would be alerting around analytics. If my reject rate goes above x% create an alert that can be seen in a global dashboard, or over something like an automated email.
Is this functionality released by Tulip ?
I want this functionality for e-signature widget.
Feature :- The system shall log failed electronic signature entries.
@Pete_Hartnett Has there been any updates on this? I think it would be great and I was just about to submit this exact idea. Personally I have found that I cant always rely on the user to alert myself if an error pops up, if it doesn’t stop them they just ignore it… So a way to get notifications if an error pops up would be amazing!
Event logs are great idea.
I also would like Tulip App to have three additional App Info data.
App Info.Last System Error Message (Text)
App Info.Last System Error Occurred DateTime(Datetime)
App Info.Last System Error Occurred Trigger Name(Text)
If they exist, App Builder could build their Apps more robust to system errors.
(Currently, system error message is only shown to the end user in red box which disappears in seconds. )
Hi @mkucker sorry for the delay here. The update I can provide is that we’re very aware of this need, and we definitely see how many folks have requested this, both from the number of votes this post has gotten and from asks throughout the customer base. Work is moving slower on this than we expected, and we’re doing our best to make sure we get this right. I can follow-up as we have more to report down the line.
I would love if there was even a delimiter separated string saved to the completion data that we could access.
A bunch of our apps broke this morning and our operators are saying they are seeing error messages infrequently and they didn’t write them down, so it’s been very difficult for us to troubleshoot the issues.
We had another issue this morning that stopped production for a period of time. The operator stated that they were getting the red Error Messages and “it said something about a table”. I reviewed the completion data with the Engineer who wrote the app and we don’t have any triggered Error Messages in that section of the app. That means this was a Tulip sent Error.
Can we have these Errors saved into the completion data?
