I suspect this is a caching issue:

Others are seeing this as well 

However, I' m not immediately sure what is the best way to invalidate the cache in this case...

I still have not found how I can make my edits immediately visible without restarting Umbraco.

Another issue I noticed: upon upgrading to Contour 3.0.20, updating member properties using ContourStrikesAgain completely stops working. Edits even completely stop showing, even in the backend member section...

Yeah must be a member cache issue, it's probably the member tools that don't update the cache correctly

I' d have to browse the Umbraco Source but I suspect there is a method to flush the cache? If anybody knows, feel free to share? I suspect I could call it as a temporary fix...

An update to this:

I upgraded my Umbraco install to 6.2.0 beta because it apparently features a new Membership Provider. At the same time, I also upgraded to Contour 3.0.20.

This broke Contour Strikes Again (which is roughly identical to Member Tools. At this stage, the Workflow responsible for updating member properties failed to map fields correctly.

For those interested, following alterations to the source code fixed that first issue:

...
string mapping = "";

if (!string.IsNullOrEmpty(a[2]))
    //mapping = record.RecordFields[new Guid(a[2])].ValuesAsString();
    mapping = record.RecordFields.Where(f => f.Value.Field.Id == new Guid(a[2])).First().Value.ValuesAsString();
...

The commented line is the original code, which did not work because the RecordFields dictionary contains the wrong guide as keys (ie not the record FieldKeys):

If somebody can tell me why this is, please tell, this code worked fine on U6.0.6 and Contour 3.0.19 ...

That left me with having to use the new Membership system of 6.2.0:

At the beginning of the WorkFlow Execute, you can call:

var ms = ApplicationContext.Current.Services.MemberService;

Some more modifications are needed:

if (int.TryParse(System.Web.Security.Membership.GetUser().ProviderUserKey.ToString(), out mId))
      {
          //Member m = new Member(mId);
          Umbraco.Core.Models.Member m = (Umbraco.Core.Models.Member)ms.GetById(mId);
...

//foreach (Property p in m.getProperties)
       foreach (Umbraco.Core.Models.Property p in m.Properties)
       {

           try
           {

               //if (mappings.ContainsKey(p.PropertyType.Alias))
               if (mappings.ContainsKey(p.Alias))

               ...

               m.SetValue(p.Alias, mappings[p.Alias]);

           }

Last but not least:

ms.Save(m);
//m.XmlGenerate(new System.Xml.XmlDocument());
//m.Save();

This restores member update functionality for the workflow but sadly, member properties are still being cached somewhere so it takes for this cache to expire before any updates become visible elsewhere on the Front End... So I still really would like to know how this can be fixed.

is working on a reply...