magicseth
magicseth2y ago

Actions transient error

I'm trying to make a new action, and this error is not helping me find my problem. I also see nothing in the logs
No description
10 Replies
lee
lee2y ago
Sorry, let me give you your own thread. I don't see any errors for dusty caterpillar. Is it possible the errors are on another deployment (maybe flip development/production)? That actions typescript certainly looks like a bug, although it shouldn't cause any runtime issues. I'll look into it
magicseth
magicsethOP2y ago
I was getting this error: source.on is not a function then I fixed it and now get the transient error
magicseth
magicsethOP2y ago
I don't see the transient error on the server logs, only in the client browser
lee
lee2y ago
Interesting. This looks like a problem on our side, but I'm having trouble finding it in logs. Maybe @nipunn can help when the west coast wakes up 🙏
magicseth
magicsethOP2y ago
it was transient it's working fine now welp that was short lived transient error is back I see wss socket with pending
magicseth
magicsethOP2y ago
No description
magicseth
magicsethOP2y ago
it seems restart gets called everytime I reload the page so if I execute my action too soon, it gets restarted, and broken setTimeout fixes my problem but I don't know root cause of restarts
lee
lee2y ago
Ah i think this is something we've seen before -- actions happening before the websocket connects and never running. A fix should be in the works, and until then I think setTimeout is a fair workaround https://discord.com/channels/1019350475847499849/1019350478817079338/1077342438370328636
presley
presley2y ago
Fix is landed and we are going to release it early next week.

Did you find this page helpful?