Sync report that has failed replication before

Technical Support
1

I have a report that fails to get replicated upstream due to replication depth rules. I get this error

Denied replicating to remote server
Object { id: “2b1d9e0f-8a75-44a5-9467-7f957b44c1bc”, error: “forbidden”, name: “forbidden”, status: 500, stack: "br@https://19…

I removed all the replication depth rules, pushed the new config and initiated a sync. I get no errors logged but the report is still missing upstream. Is there a way to get the report synced after such an error?

2

@diana can confirm, but I think you might have to edit the report to trigger a new change before the client will try to re-sync it again…

2 Likes
3

That’s correct. Just making an edit on the report will trigger a re-sync. Nothing has to be changed, just clicking the save button is sufficient.

2 Likes