# Event log to record Tulip error messages

**URL:** <https://community.tulip.co/t/event-log-to-record-tulip-error-messages/5902>\
**Category:** Product Suggestions\
**Created:** [July 25, 2022, 2:09am UTC](https://community.tulip.co/t/event-log-to-record-tulip-error-messages/5902 "2022-07-25T02:09:27Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rakitha](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/rakitha/32/4668_2.png) [@Rakitha](https://community.tulip.co/u/Rakitha)\
**Post date:** [July 25, 2022, 2:09am UTC](https://community.tulip.co/t/event-log-to-record-tulip-error-messages/5902/1 "2022-07-25T02:09:27Z")

</div>

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.

 ![windows event log](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/2X/0/0bdba008a2f7fb477024b2bda3e203f83698029d.png)

---

<div class="post-metadata">

**Author:** ![Pete\_Hartnett](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/pete_hartnett/32/3678_2.png) [@Pete\_Hartnett](https://community.tulip.co/u/Pete_Hartnett)\
**Post date:** [July 25, 2022, 11:56am UTC](https://community.tulip.co/t/event-log-to-record-tulip-error-messages/5902/2 "2022-07-25T11:56:33Z")

</div>

Hey @Rakitha -

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.

Thanks in advance!  
Pete

---

<div class="post-metadata">

**Author:** ![Rakitha](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/rakitha/32/4668_2.png) [@Rakitha](https://community.tulip.co/u/Rakitha)\
**Post date:** [July 27, 2022, 11:46am UTC](https://community.tulip.co/t/event-log-to-record-tulip-error-messages/5902/3 "2022-07-27T11:46:22Z")

</div>

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… 🙂

---

<div class="post-metadata">

**Author:** ![Pete\_Hartnett](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/pete_hartnett/32/3678_2.png) [@Pete\_Hartnett](https://community.tulip.co/u/Pete_Hartnett)\
**Post date:** [July 27, 2022, 12:14pm UTC](https://community.tulip.co/t/event-log-to-record-tulip-error-messages/5902/4 "2022-07-27T12:14:05Z")

</div>

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.

Keep the great ideas coming!  
Pete

---

<div class="post-metadata">

**Author:** ![sagar007](https://avatars.discourse-cdn.com/v4/letter/s/6f9a4e/32.png) [@sagar007](https://community.tulip.co/u/sagar007)\
**Post date:** [November 4, 2022, 1:35pm UTC](https://community.tulip.co/t/event-log-to-record-tulip-error-messages/5902/5 "2022-11-04T13:35:08Z")

</div>

Is this functionality released by Tulip ?  
I want this functionality for e-signature widget.  
Feature :- The system shall log failed electronic signature entries.

---

<div class="post-metadata">

**Author:** ![mkucker](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@mkucker](https://community.tulip.co/u/mkucker)\
**Post date:** [May 24, 2023, 1:03pm UTC](https://community.tulip.co/t/event-log-to-record-tulip-error-messages/5902/6 "2023-05-24T13:03:20Z")

</div>

@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!

---

<div class="post-metadata">

**Author:** ![ta-aoki](https://avatars.discourse-cdn.com/v4/letter/t/a587f6/32.png) [@ta-aoki](https://community.tulip.co/u/ta-aoki)\
**Post date:** [June 15, 2023, 11:04am UTC](https://community.tulip.co/t/event-log-to-record-tulip-error-messages/5902/7 "2023-06-15T11:04:17Z")

</div>

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. )

---

<div class="post-metadata">

**Author:** ![mkucker](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@mkucker](https://community.tulip.co/u/mkucker)\
**Post date:** [August 2, 2023, 1:24pm UTC](https://community.tulip.co/t/event-log-to-record-tulip-error-messages/5902/8 "2023-08-02T13:24:36Z")

</div>

@John I know you’re not part of this thread but I’ve seen you’re very active and was hoping we could get an update on this, thanks!

---

<div class="post-metadata">

**Author:** ![John](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/john/32/4971_2.png) [@John](https://community.tulip.co/u/John)\
**Post date:** [September 27, 2023, 5:18pm UTC](https://community.tulip.co/t/event-log-to-record-tulip-error-messages/5902/9 "2023-09-27T17:18:22Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![jmurray](https://avatars.discourse-cdn.com/v4/letter/j/ecae2f/32.png) [@jmurray](https://community.tulip.co/u/jmurray)\
**Post date:** [May 16, 2024, 1:19pm UTC](https://community.tulip.co/t/event-log-to-record-tulip-error-messages/5902/10 "2024-05-16T13:19:43Z")

</div>

This would be fantastic.

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.

---

<div class="post-metadata">

**Author:** ![jmurray](https://avatars.discourse-cdn.com/v4/letter/j/ecae2f/32.png) [@jmurray](https://community.tulip.co/u/jmurray)\
**Post date:** [August 26, 2024, 12:37pm UTC](https://community.tulip.co/t/event-log-to-record-tulip-error-messages/5902/11 "2024-08-26T12:37:59Z")

</div>

Bumping this suggestion higher.

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?

---

<div class="post-metadata">

**Author:** ![AdamHadlock](https://avatars.discourse-cdn.com/v4/letter/a/a88e4f/32.png) [@AdamHadlock](https://community.tulip.co/u/AdamHadlock)\
**Post date:** [November 21, 2024, 8:55pm UTC](https://community.tulip.co/t/event-log-to-record-tulip-error-messages/5902/12 "2024-11-21T20:55:56Z")

</div>

Bumping!

Would love to wire up a webhook with these events this is a common pattern. Check out how twilio does this for an example.

---

<div class="post-metadata">

**Author:** ![jef.vanhoutven](https://avatars.discourse-cdn.com/v4/letter/j/8491ac/32.png) [@jef.vanhoutven](https://community.tulip.co/u/jef.vanhoutven)\
**Post date:** [January 28, 2025, 7:46am UTC](https://community.tulip.co/t/event-log-to-record-tulip-error-messages/5902/13 "2025-01-28T07:46:49Z")

</div>

It would be great if we can get an overview of all the errors that occurred in the entire environment, without having to rely on the operator to pass the error message

---

<div class="post-metadata">

**Author:** ![jmurray](https://avatars.discourse-cdn.com/v4/letter/j/ecae2f/32.png) [@jmurray](https://community.tulip.co/u/jmurray)\
**Post date:** [March 14, 2025, 1:04pm UTC](https://community.tulip.co/t/event-log-to-record-tulip-error-messages/5902/14 "2025-03-14T13:04:43Z")

</div>

Bumping again.

When the User ID issue happened last week we got a lot of “Tulip’s broken. A red box popped up” complaints. Seeing as it was a plant wide issue, we could assume what was happening. However, it would be really nice to be able to check logs.

---

<div class="post-metadata">

**Author:** ![canaalpaslan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/canaalpaslan/32/6653_2.png) [@canaalpaslan](https://community.tulip.co/u/canaalpaslan)\
**Post date:** [March 17, 2025, 8:46am UTC](https://community.tulip.co/t/event-log-to-record-tulip-error-messages/5902/15 "2025-03-17T08:46:12Z")

</div>

Hey everyone,  
Thank you for the amazing input here, we are well aware of this need and are doing active discovery in this area. I will reply to the thread here with more to share in a few months.

Couple of questions from my end in the meantime:

- Are you looking to collect this information for troubleshooting purposes, or for a specific period afterward to review runs?
- Are you looking to export this data to another system (i.e. log management)?

Thanks!

---

<div class="post-metadata">

**Author:** ![ta-aoki](https://avatars.discourse-cdn.com/v4/letter/t/a587f6/32.png) [@ta-aoki](https://community.tulip.co/u/ta-aoki)\
**Post date:** [March 17, 2025, 9:05am UTC](https://community.tulip.co/t/event-log-to-record-tulip-error-messages/5902/16 "2025-03-17T09:05:23Z")

</div>

> - Are you looking to collect this information for troubleshooting purposes, or for a specific period afterward to review runs?

Both.

> - Are you looking to export this data to another system (i.e. log management)?

Yes. CSV would be fine.

---

<div class="post-metadata">

**Author:** ![Nicolas](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/nicolas/32/3349_2.png) [@Nicolas](https://community.tulip.co/u/Nicolas)\
**Post date:** [March 17, 2025, 3:16pm UTC](https://community.tulip.co/t/event-log-to-record-tulip-error-messages/5902/17 "2025-03-17T15:16:36Z")

</div>

Hi  
For us,  
1/ Are you looking to collect this information for troubleshooting purposes, or for a specific period afterward to review runs?  
Be live alerted, troubleshoot issue afterward 3-5 days retention, analytics (ie: get per apps or users or connector, number of alert per week, per month to put in place action like end-user training, UI change, validation rule on input widget, bug fixing…)  
2/ Are you looking to export this data to another system (i.e. log management)?  
Yes in external log management (like Datadog) for log display (combine with log of other system integrated with Tulip), monitoring heath with a dashboard and be alert by email/pagerDuty on issue threshold.

---

<div class="post-metadata">

**Author:** ![HCZuo](https://avatars.discourse-cdn.com/v4/letter/h/839c29/32.png) [@HCZuo](https://community.tulip.co/u/HCZuo)\
**Post date:** [April 14, 2025, 1:06pm UTC](https://community.tulip.co/t/event-log-to-record-tulip-error-messages/5902/18 "2025-04-14T13:06:34Z")

</div>

Hi,

I think these features will be used by us to evaluate whether our APPs have worked correctly. As several people have mentioned, we can’t rely on the operators to send us some error messages… It would be much better to know where the errors are and how they appeared. Out APPs crashed last week for a while and we definitely want to avoid it via the log information.

---

<div class="post-metadata">

**Author:** ![ta-aoki](https://avatars.discourse-cdn.com/v4/letter/t/a587f6/32.png) [@ta-aoki](https://community.tulip.co/u/ta-aoki)\
**Post date:** [November 26, 2025, 2:37am UTC](https://community.tulip.co/t/event-log-to-record-tulip-error-messages/5902/19 "2025-11-26T02:37:12Z")

</div>

It would also be great if these “connection issue” and “trigger running so long” type of events logged temporary inside the Player and uploaded to the server once connected so that Account Owners can review these problems.

> **[Platform Release 316 - April 2025](https://support.tulip.co/docs/platform-release-316-april-2025)**

 ![image](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/2X/7/7ef4f79ee72cedcac454ae5d6c2bae3a2a7d224d.png)

> **[Platform Release 331 - August 2025](https://support.tulip.co/docs/platform-release-331-august-2025)**

 ![image](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/2X/4/453c03ad35084cbee7cac7dd8acb43cc3ad7410a.png)
