That’s generally a temporary error, intermittent and non-permanent communications issue.

Is it persisting, or was it only a small timeframe occurence?

It doesn't always happen, and it happens in different jobs.
But it happens in several jobs.
I am migrating from another backup software and this did not happen, so I rule out infrastructure problems

interesting.  Something like this can have several causes from resource allocation, to bandwidth, to concurrent jobs/streams.

Can you open a support case and share the number here?  It’s better to have someone check the logs and do a deep dive into your issue.

Hi, I am from the Indexing team. As Mike pointed out, if we have an escalation , we can identify the root cause and resolve the issue. 

@Gustavo I’m marking this as solved since I do not see any escalation on your end.

If this happens again, please let us know!