SmartRule Corrupted Dictionary

My logs show these two errors

Is this a problem with Trickster and Reminders, or is this a problem with DT3 3.9.4?

It’s the only report we’ve seen. What’s the Reminders smart rule?

What is odd is I deactivated the Reminders rule and I am still getting the error- that is odd

It is:

And this is the script:

on performSmartRule(selection)
	
	set listName to "From Devonthink"
	
	tell application id "DNtp"
		
		
		set selectedItems to selection
		repeat with theItem in selectedItems
			set itemName to the name of theItem
			set itemUUID to the uuid of theItem
			
			if first character of itemUUID is "<" then
				set itemUUID to my cleanUUID(itemUUID)
			end if
			set itemCallback to "x-devonthink-item://" & itemUUID
			set itemHasDueDate to false
			
			
			try
				set dueDate to due date of reminder of theItem
				set itemHasDueDate to true
			end try
			
			
			tell application "Reminders"
				set myList to list listName
				tell myList
					if itemHasDueDate is false then
						make new reminder at end with properties {name:itemName, body:itemCallback}
					else
						make new reminder at end with properties {name:itemName, body:itemCallback, due date:dueDate}
					end if
					
				end tell
			end tell
			
		end repeat
		
	end tell
	
end performSmartRule

on cleanUUID(itemUUID)
	set itemUUID to texts 2 thru -1 of itemUUID
	set itemUUID to texts 1 thru -2 of itemUUID
	
	set itemUUID to "%3C" & itemUUID & "%3E"
	
	return itemUUID
end cleanUUID

There was a similar report:

It might instead be this Reminders rule:

with this script:

on performSmartRule(theRecords)

tell application id “DNtp”

set due_date to current date

set due_date to due_date + 3600 * 24

repeat with theRecord in theRecords

tell theRecord to make new reminder with properties {schedule:daily , alarm:sound , due date:due_date}

end repeat

end tell

end performSmartRule

Do you use DEVONthink 3.9.4, does a reboot fix this? I noticed similar issues also few times with other apps (e.g. Safari) on Sonoma.

I rebooted and that particular error stopped

Now I get this

I am guessing there is some issue with Sonoma and the Trickster integration as this has been rock solid for a long time

Did you modify this rule or its script? Or is identical to the one from the support assistant?

2 years ago soon after the integration was released I made a couple of minor edits to the script at the direction of Apparent Software so that it would recognize new Groups as well as new documents. I think their plan was to make that the “standard” script at some point but I do not know if that happened.

For that reason my script has a portion commented out to remind me of what used to be there before my current version.

This has worked well for over 2 years now.

For what it’s worth the errors in the log do seem to be decreasingly quite notably in frequency - is there some indexing that goes on an thus it is self-repairing?

on performSmartRule(theRecords)

tell application id “DNtp”

repeat with theRecord in theRecords

set itemLink to the reference URL of the theRecord

set thePath to the path of the theRecord

set recordPath to the location of theRecord

set appname to name

tell application “Trickster”

add recent thePath source appname displayPath recordPath callbackURL itemLink bundleID “com.devon-technologies.think3”

end tell

(* set itemLink to the reference URL of parent of theRecord

set thePath to the path of parent of theRecord

set recordPath to the location of parent of theRecord

set appname to name

tell application “Trickster”

add recent thePath source appname displayPath recordPath callbackURL itemLink bundleID “com.devon-technologies.think3”

end tell

*)

end repeat

end tell

end performSmartRule

Not in DEVONthink. But the script retrieves the path of the record which might be an empty string in case of internal groups. This would explain the most recent error, maybe the latest versions of Trickster now throw an error instead of silently failing?

Perhaps so.

Or perhaps there is some change in Trickster that works with “new data” but not old data and it thus is self-correcting because the Trickster data is transient and not retained long-term.

I will see how the trend goes and if this problem persists.

Thanks.