Failing Script is attached to Button “Duplicate Step and Actions” here: . | Fibery
FYI I resolved this - it was caused by some bugs in my use of Promises.
It would be really great to get better diagnostics than simply “Internal Server Error”
When this happens, our console.log output is not displayed, so we having no clues to follow.
Could you please share example of misuse of promise in your case, so we can reproduce and see if we can support
console.log in activity in that case as well?
Probably with a last improvement I’ve covered not all types of errors. Hoped that
console.log statements are written in activity now even when script fails.
Well I dug deeper. In case of unhandled promise rejection our script execution engine just fails and we do not have good workaround here. We can just play with the text in error message. e.g. write smth like “Executor terminated unexpectedly”, which is actually what happened. Sorry for that.
@Sergey_Truhtanov, I was unable to reproduce the 500 error – hopefully that is good news!
It will work with any entity in the table - just open an entity and execute the Button script called “Causes Server Error 500”
It would also be very helpful if this error would log accumulated console.log() messages:
Failed to execute action "Script": Unable to complete execution during 20000 ms
There is little can do to debug this issue further on my own.
As it is, I can afford to wait around indefinitely for someone to fix this, some day because my Workspace is just for my own research at this point.
But if my Workspace was a client production system, this would be an untenable situation.
I am happy to provide additional information if that is helpful. I have supplied a test case that reliably reproduces this “500 Internal Server Error”, and ten days later there is still no response from the Fibery team.
As a software developer, this does not leave me confident that I can build a production system on this platform, and know that I will receive critical support from the dev team to fix any show-stopper bugs that arise, in a timely manner.
We don’t have access to your workspace by default, so we can’t see the example
Sorry, I just assumed the team would have some kind of super-admin access to everything.
I am happy to share access to my Workspace with the Fibery Team - just let me know who to add.
We should have mentioned this sooner, sorry. I hope @Sergey_Truhtanov might be able to help (or find someone else who can)
(post deleted by author)