Readwise not syncing

[tenderloin]

I've double-checked the token but no files are being created on the initial sync. Is there a log I can supply? Any other information that might help?

[yhoebeke]

I also have the same issue. I set custom templates and entered my token. I get the notification but no files are synced.

[renehernandez]

By initial sync are referring to syncing when you start the Obsidian app? The plugin won't sync automatically when installed for the first time.

To confirm, can you add a new highlight into Readwise and then execute the sync command from the command palette?

Most likely, the issue is with the message, which I have to improve.

The plugin will sync only new documents and highlights since it was installed, as explained on the How the Sync Process work section.

[yhoebeke]

Hello @renehernandez ,

Here is the process I just went through:

1. I created a new highlight on readwise
2. I launched the command to sync highlights again: it synced the last highlight I just made!
3. I deleted the files just to see how the plugin would behave (and because I wanted to reformat the headings)
4. I relaunched the command but nothing got synced.
5. I created a new highlight and resynced : only the new highlight note was created.

So indeed, as you explained in the link you provided, only the highlights since the plugin was installed will be synced, or even last synced. So I guess it's best not to deleted any highlights from the vault or we won't be able to sync them again, correct?

On a side note, I noticed the dates don't use the default daily note format of the vault. I noticed the "bug" as the link didn't point to the correct daily note. Perhaps this could fix by adding a field to indicate the user's daily note naming format.

[renehernandez]

Are you looking for a way to extract the week day as well? That would require some computation within the plugin, because at the moment, the value of the updated field is provided as is

[thomasvs]

Hello @renehernandez ,

Here is the process I just went through:

1. I created a new highlight on readwise
2. I launched the command to sync highlights again: it synced the last highlight I just made!
3. I deleted the files just to see how the plugin would behave (and because I wanted to reformat the headings)
4. I relaunched the command but nothing got synced.
5. I created a new highlight and resynced : only the new highlight note was created.

So indeed, as you explained in the link you provided, only the highlights since the plugin was installed will be synced, or even last synced. So I guess it's best not to deleted any highlights from the vault or we won't be able to sync them again, correct?

On a side note, I noticed the dates don't use the default daily note format of the vault. I noticed the "bug" as the link didn't point to the correct daily note. Perhaps this could fix by adding a field to indicate the user's daily note naming format.

If I follow this correctly, there is no way at all to have this plugin sync in all my readwise higlights that I had before I first install this plug-in? That seems like a huge limitation if I can't get started with my existing highlights. Is this fundamentally impossible or just not implemented?

[renehernandez]

@thomasvs You can always manually export your Readwise highlights using the Markdown exporter.

Is this fundamentally impossible or just not implemented?

It isn't implemented. Issue #7 tracks this, but it is almost a project on its own. I would rather prefer that the Readwise folks implemented this since it is core to them 😂

[renehernandez]

@yhoebeke

So I guess it's best not to deleted any highlights from the vault or we won't be able to sync them again, correct?

For now yes, that is correct.

[technicalpickles]

I took a look at #7 and I'm not sure I am following what the limitation of how the API client in https://github.com/renehernandez/obsidian-readwise/blob/main/src/api/api.ts is a blocker to pulling in highlights before the time you installed.

@renehernandez could you elaborate on the problem?

[renehernandez]

@technicalpickles Because you may have many more highlights that the 1000 limit that can be pulled on a single request.

Adding a Sync all command requires that the API can manage pagination of requests and support for wait if the rate limit is reached as mentioned in #7.

I have one feature left (Authors mapping) before tackling this, so it is close