Lisa, hear me out, because I'm struggling with this. I hope you've seen that I have a strong, genuine desire to help anyone without prejudice. I even go beyond what most are willing to do in terms of providing direct, marketable expertise towards resolving issues directly within templates and solutions (that's the point at which payment is typically expected). I haven't really drawn my line, because I'm new to the "giving" side of SharePoint/InfoPath after years of only consuming. However, this situation is giving me pause. Please verify that I have these factoids right:
-
You and an entire team of people are being paid by a client as IT consultants to deliver some solution or set of solutions within SharePoint that includes InfoPath
-
Your team has the ability, rights, and responsibility to fix the broken "portal," which means to me that your team is the one who architected it, built it, and maintains it. Is some of that not true? Is that portal a client portal that you were paid to deliver?
-
You were working on something close to the deadline that I was able to help you figure out
-
You know exactly what is causing your problem and keeping you from delivering the desired solution
-
You can't or aren't willing to try and fix the root of the problem, which is the responsibility of your team anyway (maybe?) due to perceived time constraints
-
You present to the client tomorrow and are asking random strangers to provide a solution to you overnight for free in their free time that can be presented to your client - the client who will pay for your entire team's work that was actually solved by the unpaid stranger
Am I off? I have a hard time helping, and I know that the folks who run this forum are incredibly talented (several MVPs and near-MVPs) - probably well-beyond my own talent. However, they do this for a living and have an entire service that allows customers to pay for them to solve problems through consulting or through development (code or not). The even worse part is this is not an InfoPath issue, but rather a SharePoint admin/architecture issue that is causing an SPD issue, so it's not relevant to this forum at all really.
I'm not saying I could even think up an alternative solution overnight or even in weeks. What I do know is that if you are trying to deliver or present something on that broken portal, you have far more things to worry about than paused workflows. The Timer Service is critical to the health and success of SharePoint as a whole. If it's busted, then the entire list of timer jobs will not run - indexing, alerts, and tons of other jobs. My opinion is that the moment you became aware of that being the root cause, it needed to be addressed with the full attention of everyone even if it meant getting an expert architect online for a fee. That wasn't done, but i still contend that the best way to fix this is to at least LOOK for some simple solutions to fixing the Timer Service, because that would fix a lot of other things while also allowing your pause duration workflow.
You may have just left out the fact that your team already did some basic troubleshooting, but I think that if I had the chance, I could have a decent shot at figuring it out quickly enough for you to present on time. You could concurrently look for alternative workflow solutions, but I imagine it will require custom coding from scratch for the whole workflow.
</soapbox>