Bug with boundary event and inclusive gateways

Hi! I found strange behavior of inclusive gateway under specific conditions. Please look at the image below.
When timer boundary event is running out of time, execution goes to GW1 and then back to task1.
At this point a new instance of task1 must appear, but it doesn’t. Now if you complete task1, the process stucks at GW2. As I understand, GW2 waits for second token here but it will never come because there’s only one instance of task1.
If you change GW1 from inclusive gateway to exclusive, new instance of task1 appears at every boundary timer run as expected.
Here’s a process model