Hi Domini, Ragav is correct. You can also try checking transaction SLG1 object WF to see if any error messages are showing up there. Apart from that make sure you catch exceptions, especially abort messages and raise a workflow exception (e.g. an exception of your BOR method) so that workflow is advised of the problem. E.g. you could use a TRY.. CATCH statement in your BOR method to capture and report the exception that caused the dump.
Regards
Jocelyn