As @caltang mentioned, without context we cannot really tell much. This is an error that is rare but pops up when something is broken. There can be many reasons this happens, and most times when I have encountered this error, it was resolved by changing the approach I was taking in my workflow.
Check if you are hitting memory limit, see if any tool is generating a large data and consuming lot of memory. If you are using db, see if you are not taking in large amount of data.
Turn off AMP and try once.
Break the workflow into chunks to identify where it is occurring, add containers in steps let's say three big containers, keep only first one on and run the workflow. If it runs successfully then turn on just first and second and run again and so on. You will know which piece is breaking it.
If nothing helps, as @alexnajm suggested, raise a ticket.
