gistfile1.txt

1. Does this(why the tasks not being picked up) relate in any way with the high memory usage? Or do you think, the memory usage as such not an issue?
Memory usage is not a concern until foreman tasks start failing or if you see other issues. In this specific scenario the foreman tasks (other than those capsule sync tasks) were progressing quickly and seem to be fine.

2. Is the dynflow executor in some way related with the tasks "monitor events queue"&"Listen on candlepin events"? Actually I guess a third question:)
These two tasks do subscription related work and few other tasks - the dynflow executor itself is not dependent on these tasks.

3. I'm just asking myself if this situation could not have been fixed by restarting one of the two processes "monitor events queue"&"Listen on candlepin events"...
In the past for the issues around these tasks, the reliable solution which worked consistently is the removal of tasks and restarting foreman-tasks.