When I use the capture assistant to schedule a regular backup, I'm getting stuck at the "Size Limit" page. Clicking on continue doesn't take me to the next page, so I can't complete the backup strategy.

It seems to me that this was working in earlier versions, but I can't progress past this step.

I can't reproduce the problem here, but here are couple of things to check.

Look for error messages in the console log. These would occur at the time you tried to move to the next page in the assistant.

Move all of the files in ~/Library/Preferences/QRecall/Actions/ to another location and try the assistant again. If that works, put them back and see if it gets stuck again.

Nothing in the log from previous attempts.

I removed the preferences/actions and then the capture assistant worked OK.

Put the actions back and the same error occured again.

Now had some entries in the log that seem to refer to "your" development environment:

2007-09-13 08:14:16.048 QRecall[334] *** Assertion failure in -[RepositoryAliasReference path], /Users/james/Development/Projects/Quantum Recall/Common/Source/Actions/RepositoryPathReference.m:112
2007-09-13 08:14:16.060 QRecall[334] -[RepositoryPathReference path]: pathToRepository is nil
2007-09-13 08:14:16.736 QRecall[334] *** Assertion failure in -[RepositoryAliasReference path], /Users/james/Development/Projects/Quantum Recall/Common/Source/Actions/RepositoryPathReference.m:112
2007-09-13 08:14:16.740 QRecall[334] -[RepositoryPathReference path]: pathToRepository is nil
2007-09-13 08:14:17.376 QRecall[334] *** Assertion failure in -[RepositoryAliasReference path], /Users/james/Development/Projects/Quantum Recall/Common/Source/Actions/RepositoryPathReference.m:112
2007-09-13 08:14:17.380 QRecall[334] -[RepositoryPathReference path]: pathToRepository is nil
2007-09-13 08:14:17.984 QRecall[334] *** Assertion failure in -[RepositoryAliasReference path], /Users/james/Development/Projects/Quantum Recall/Common/Source/Actions/RepositoryPathReference.m:112
2007-09-13 08:14:17.992 QRecall[334] -[RepositoryPathReference path]: pathToRepository is nil
2007-09-13 08:14:18.720 QRecall[334] *** Assertion failure in -[RepositoryAliasReference path], /Users/james/Development/Projects/Quantum Recall/Common/Source/Actions/RepositoryPathReference.m:112
2007-09-13 08:14:18.725 QRecall[334] -[RepositoryPathReference path]: pathToRepository is nil
2007-09-13 08:18:25.338 QRecall[1802] *** Assertion failure in -[RepositoryAliasReference path], /Users/james/Development/Projects/Quantum Recall/Common/Source/Actions/RepositoryPathReference.m:112
2007-09-13 08:18:25.338 QRecall[1802] -[RepositoryPathReference path]: pathToRepository is nil
2007-09-13 08:18:26.032 QRecall[1802] *** Assertion failure in -[RepositoryAliasReference path], /Users/james/Development/Projects/Quantum Recall/Common/Source/Actions/RepositoryPathReference.m:112
2007-09-13 08:18:26.046 QRecall[1802] -[RepositoryPathReference path]: pathToRepository is nil
2007-09-13 08:18:26.704 QRecall[1802] *** Assertion failure in -[RepositoryAliasReference path], /Users/james/Development/Projects/Quantum Recall/Common/Source/Actions/RepositoryPathReference.m:112
2007-09-13 08:18:26.712 QRecall[1802] -[RepositoryPathReference path]: pathToRepository is nil
2007-09-13 08:18:27.304 QRecall[1802] *** Assertion failure in -[RepositoryAliasReference path], /Users/james/Development/Projects/Quantum Recall/Common/Source/Actions/RepositoryPathReference.m:112
2007-09-13 08:18:27.312 QRecall[1802] -[RepositoryPathReference path]: pathToRepository is nil

Here's the problem: After the assistant gathers the archive size information, it checks to see if the actions it is about to create will duplicate actions that have already been created. It does this by reading all of the action files. The assistant isn't progressing, but that process is throwing errors.

So, I know what's going wrong I just don't know why. The error says that your action references contain nil paths to the archives -- something that should never happen.

Would you mind zipping up your action files in ~/Library/Preferences/QRecall/Actions and sending them too me so I can examine them? There seems to be something odd about them.

Never mind, John. I was able to reproduce the problem. I'll have a fix for this in the next release.

In the mean time, you can avoid this bug by first creating the new archive using the File > New Archive command, then use the assistant to create the capture strategy.