How to sync your Ravelry stash and projects with Stashora

Connecting Ravelry gives Stashora access to connected features such as your library, favorites, queue, and forums. It does not mean every item on your device is automatically written back to Ravelry.

Supported stash and project information can move in both directions. You review the proposed changes before they are applied. Local organization also works without Ravelry, so you can decide when a record should participate in a connected workflow.

Sources: Stashora on the App Store

Start with records you recognize and changes you can easily verify. The aim of the first review is to understand the direction of each update and which version of the information you want to keep.

• Confirm you connected the intended Ravelry account, especially if you use more than one.
• Look over your existing Ravelry stash and projects so you can recognize them in the proposed import.
• Check whether you already created the same yarn or project locally. Resolve unclear matches before confirming changes.
• Keep an internet connection available while reviewing and applying changes.

This is a review checklist, not a promise that every Ravelry field is supported. The current sync preview is the place to inspect the changes supported by your installed version.

1. Inspect incoming changes. Check that the yarn or project is the record you intended to bring into Stashora.
2. Inspect outgoing changes. Confirm the proposed Ravelry update matches the local edit you want to publish.
3. Resolve conflicts. Where local and Ravelry versions differ, choose the information you want rather than assuming the most recent-looking record is correct.
4. Confirm only after the proposed changes make sense. Do not assume a field was included if it does not appear in the review.
5. Check the result in Stashora and Ravelry. For quantities, verify the value as well as the unit and what the number represents.

Imagine your local record says 80 grams remain and your Ravelry record says 100 grams. Those values may reflect a real project update, an older estimate, or a different way of recording quantity. Choosing a side before checking the yarn could preserve the wrong value.

Weigh the remaining yarn, check whether any is set aside for another project, and choose the appropriate value in the supported conflict review. After syncing, check the result. This example illustrates the decision; it does not imply that grams are mapped to every Ravelry quantity field.

Check the connection, the Ravelry account and the proposed changes first. Then check whether the change was included in the preview and actually confirmed. A local edit and a completed Ravelry update are separate states.

If the result is still unclear, keep the record name, the change you expected, and any error message. Contact Stashora support before retrying a large set of uncertain edits. Avoid creating a second copy simply because an update has not appeared yet.