# Platform Release 383 - August 2026 **URL:** \ **Category:** Announcements\ **Created:** [August 27, 2026, 4:25pm UTC](https://community.tulip.co/t/platform-release-383-august-2026/16536 "2026-08-27T16:25:16Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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:** [October 7, 2026, 3:16am UTC](https://community.tulip.co/t/platform-release-383-august-2026/16536/2 "2026-10-07T03:16:30Z")
How is this fixed? Does it now just stop retrying, or does it now discard with some kind of notification to the users? > _PLAT-56349 Fixed an issue where an app completion that failed to save for a permanent reason (for example, a value too large for its column) was retried until the retry limit was reached and then discarded silently._ It would be also great if those issues can also be viewed from the suggested event logs. > [@Event log to record Tulip error messages](https://community.tulip.co/t/event-log-to-record-tulip-error-messages/5902): > > 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 … --- _[View the full topic](https://community.tulip.co/t/platform-release-383-august-2026/16536)._