08-14-2024 07:49 AM
Only recently I have needed to Refresh the Connection in ShipConnect. Up until a few weeks ago this was not an issue. I tend (past tense now) to print remotely and so what I now error each morning without a refresh I need to log into my computer rather than print though the website. I would like SS to maintain the connection between SS and the ship connect
08-19-2024 08:40 AM
Any chance you've recently updated ShipStation Connect? We did and have had nothing but problems. We are trying to figure out a way to revert back to an older version for A / B testing.
08-21-2024 01:45 PM
Hello @Jenniferdb1!
Thank you for your post. We should be rolling out updates to the SS Connect in the next few weeks.
Stay tuned for more updates.
Happy Shipping!
-Cara
08-22-2024 10:20 AM
The update from today (August 22, 2024) did nothing to fix our problems.
08-26-2024 03:37 AM
I have had the refresh issue come up in the last week or so as well and the latest update-8/25/24-did nothing for that issue and now I can't even use the help center so I had to email support, just like the last few times we have had issues with Connect
08-26-2024 12:10 PM
Hello @df63!
Thank you for posting in the community! I noticed you already have a support ticket open, and they’ve asked you a few follow-up questions. They're the best team to help you with this, as they can properly troubleshoot and diagnose the issue.
I hope they can find a solution for you!
Happy Shipping!
-Cara
08-27-2024 10:30 AM
Shipstation connect keeps getting disconnected for us, very intermittent. There are days it works fine, today it does not.
08-27-2024 01:48 PM
Hello @Nguyen!
Thank you for your post in the community. I understand how frustrating this can be. The next time you encounter this issue, I recommend reaching out to support so they can help identify any patterns that might be causing SS Connect to disconnect.
Happy Shipping!
-Cara
08-27-2024 03:43 PM
Our ShipStation service has a whole is worse today than it was 30 days ago. And considerably worse than it was 2 years ago. Support to this point has provide zero fixes.