Got kicked off last week after 9 mins

Site Development Issues
1

Hey, been meaning to post this all week.

My stream was disconnected last week after 9 minutes, and I couldn’t restart it.

I didn’t appear to have an issue with my stream or any other platform.

Paul

2

Dang, that sucks! Sorry :frowning:

Thank You for the report! :folded_hands:

It’s super hard to try to fetch logs from this far back as most of the actual server logs have already rotated by now but I’ll look into this. I don’t exactly see how this could happen but I do know that we can fix at least being able to restart/continue an event if it has been for some reason ended prematurely.

I’ll make this a priority. The events should be bulletproof, always, zero exceptions.

There’s no good documentation about how the starting and ending process works and for artist the log trail is invisible as well. We need these at least:

  1. Document properly how the event start and end process works (behind the scenes)
  2. Add visible logs for artists that show ALL actions, user and system regarding important stuff like event starts and ends. Make sure these are easy to read from the artist page + via the API and MCP server.
  3. Store above logs for debugging purposes for ~30 days.
  4. Allow changing event status backwards from ended to scheduled within a certain time period like 30 mins to make it possible to “oh, fuck, I spent time prepping this event but it stopped prematurely and now I want to restart it”, make proper UI controls for this.
3

These fixes have been implemented! :rocket:

  1. We have a new Activity Log for both user and artist. This is the initial implementation, so not everything is in place yet, but all the important data regarding artist and event changes are logged and visible via the artist Activity Log page. These are also queryable using AI via our MCP server.
  2. Stopped scheduled events can now be resumed within 30 minutes of stopping. This has automation tests so that resuming actually also works properly.
  3. Slipmat Docs have been updated to cover these changes and to explain how events work in more detail.

There is no mechanism currently that explains what happened to your set but if something like this happens ever again, we have much better tools to recover from the issue and debug / understand it properly afterwards.

Again, sorry for the inconvenience, and Thank You for the report! We now have much better site thanks to it :victory_hand:

4

Thank you. No issues this week. In fact, there must have been a short glitch that saw my stream on Twitch and Mixcloud die. But the Slipmat feed sailed through it with no problem. :+1:t2::+1:t2::+1:t2: