Steffen Bleher I don't think the problem is related to availability time. I say this because, when I started using the app a few days ago, the first tag I created to organize myself was "tasks."

As you can see in the image (with an icon), if I create the same tag again, regardless of the time, it duplicates.

The first tag was sent via API, but instead of using the original tag, it created a new one. Every time I send it via API, it keeps duplicating.

Later, I manually marked the same tag in my daily notes.

If you check the next two instances, the tag was sent via WhatsApp. Despite the longer time interval, a new tag with the same name was created again.

I also tested it via Telegram, and it didn't use the existing tag either—instead, it duplicated it.

I believe preventing the creation of tags with duplicate names could potentially solve this issue.

Steffen Bleher I'm having similar issues, but inconsistently so. I created a tag called "ToRead" a few days ago, and it's been working consistently when I send links from WhatsApp and from the Capacities Chrome extension tagged with #toread. But then I created a tag called "Futurepolis links", and when I tag things with #futurepolislinks it creates a new tag in Capacities with that name each time I send. I tried the same with #FuturepolisLinks and the same occurs, with the capitalization. In the screenshot attached, the bottom three examples are things I tagged manually within Capacities; the ones above are all sent via either WhatsApp or the Chrome extension, and as you see from the colors each one is a new tag.

Junior Ribeiro: Thanks for sharing. We'll have a look!

Steffen Bleher Just updated the app and tried to send a link through Whatsapp desktop app with #a-processar tag. It created a duplicate tag and didn't add the link (screenshots attached).

Paulo Fehlauer could you try again a bit later? does it use one of your existing tags now?

Steffen Bleher .

Steffen Bleher I changed the tag to 1 word (#pendente instead of #a-processar) and my API imports seem to be working correctly now, without creating duplicate tags (don't know if that was the reason, though).

In spite of that, Whatsapp and Telegram sharing are still not working. The existing tag is now recognized, but no weblink was created in both trials.

Luca Joos I'm having a similar issue here. I wrote a script that auto-imports Readwise Reader highlights to Capacities via API, applying a "to-process" tag, which I also use in items added via Telegram / Whatsapp, so I can work on them later. It was working fine until a few days ago, but now every item added with either method creates a new "to-process" tag, which basically ruins my entire logic.

Luca Joos Thank you for addressing this. I would like to propose an enhancement based on a related request I shared on Canny last year.

Currently, text messages forwarded from WhatsApp or Telegram to Daily Notes appear with a prefix indicating the source app (via a small icon) and the time of sending. While this is helpful, it would be significantly more valuable if the timestamp were recognized as a proper time marker (e.g., @time), allowing it to appear in the timeline.

This feature would greatly benefit users like myself who track daily activity logs for productivity review and introspection. At present, timestamps are neither automatically recognized, nor does manually adding @now convert the entry into a timestamp. Enhancing this functionality could align Capacities with other productivity and bookmarking applications that integrate time and location data into their notes, enabling better context and insight.

Moreover, many Capacities users already utilize "Places/Map" objects. Integrating this feature would allow users to tag locations (e.g., @Tokyo, @Mumbai) alongside timestamps (e.g., @now or @7:30 PM), offering a more precise representation of when and where an activity or thought occurred.

Capacities' seamless integration with popular chat and email apps makes it an exceptional tool for capturing ideas and activities. Adding timestamp recognition, whether through auto-detection or manual entry, would further enhance its usability and align it with contemporary productivity tools.

Here is the detailed ticket for this feature request: https://capacities.io/feedback/p/enhancing-temporal-context-recognition-in-daily-notes-for-data-fetched-from-chat