<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: SPD workflows: &#8220;ERROR: request not found in the TrackedRequests&#8221;</title>
	<atom:link href="http://www.cleverworkarounds.com/2009/06/28/spd-workflows-error-request-not-found-in-the-trackedrequests/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cleverworkarounds.com/2009/06/28/spd-workflows-error-request-not-found-in-the-trackedrequests/</link>
	<description>After much frustration, it seems DEFAULT is the way to go...</description>
	<lastBuildDate>Thu, 02 Feb 2012 17:45:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: CleverWorkarounds &#187; Its email integration captain, but not as we know it (problems with incoming email handling on SharePoint 2010)</title>
		<link>http://www.cleverworkarounds.com/2009/06/28/spd-workflows-error-request-not-found-in-the-trackedrequests/comment-page-1/#comment-73236</link>
		<dc:creator>CleverWorkarounds &#187; Its email integration captain, but not as we know it (problems with incoming email handling on SharePoint 2010)</dc:creator>
		<pubDate>Tue, 21 Dec 2010 09:33:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.cleverworkarounds.com/?p=1440#comment-73236</guid>
		<description>[...] SHAREPOINT/system. Hmm – that sort of error message is very similar to race conditions seen with SharePoint Designer workflows. Thus, my first thought was that email enabling the Drop-off library was possibly unsupported. I [...]</description>
		<content:encoded><![CDATA[<p>[...] SHAREPOINT/system. Hmm – that sort of error message is very similar to race conditions seen with SharePoint Designer workflows. Thus, my first thought was that email enabling the Drop-off library was possibly unsupported. I [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

