Diagnosing 500 error on server-to-server replication

Hello @rygregg,
One issue that’s common with replication failures is schema conflicts.
This also might be useful:

Yep ‘drop-non-retryable-data’ fixed it for me! I had been playing with writing batch data and made a mistake, and that held up the queue. Once I updated the replication with that flag I could see the sync queue size dropping and eventually could see the data come through to the cloud
Also you might want to to monitor your replication queue size to see if data is getting stuck:

influx replication list --org-id <OSS org ID> --token <OSS token>

Also you might want to look at: