In this episode from the newer CGI-animated series, the team works on a significant community landmark.
Teamwork, problem-solving, and rectifying mistakes. Content Ideas:
You can often find these episodes on platforms like ITVX or via the Bob the Builder IMDb episode list .
Educational content focusing on how Bob repairs a "historical" object compared to modern buildings. Resources for Watching or Creating Content
Depending on the region or broadcast order, episode 43 is sometimes identified as "Ship Shape".
Watch Bob-e43a Apr 2026
In this episode from the newer CGI-animated series, the team works on a significant community landmark.
Teamwork, problem-solving, and rectifying mistakes. Content Ideas: Watch bob-E43A
You can often find these episodes on platforms like ITVX or via the Bob the Builder IMDb episode list . In this episode from the newer CGI-animated series,
Educational content focusing on how Bob repairs a "historical" object compared to modern buildings. Resources for Watching or Creating Content Watch bob-E43A
Depending on the region or broadcast order, episode 43 is sometimes identified as "Ship Shape".
This could have to do with the pathing policy as well. The default SATP rule is likely going to be using MRU (most recently used) pathing policy for new devices, which only uses one of the available paths. Ideally they would be using Round Robin, which has an IOPs limit setting. That setting is 1000 by default I believe (would need to double check that), meaning that it sends 1000 IOPs down path 1, then 1000 IOPs down path 2, etc. That’s why the pathing policy could be at play.
To your question, having one path down is causing this logging to occur. Yes, it’s total possible if that path that went down is using MRU or RR with an IOPs limit of 1000, that when it goes down you’ll hit that 16 second HB timeout before nmp switches over to the next path.