Please wait: Is There A Problem Here?: Please wait

Showing posts with label Please wait. Show all posts

20140122

Problem ID: 12670286165282783
Entered by: Ben Simo

Healthcare.gov still says "Please wait"

I tried to resume a Healthcare.gov application I abandoned a couple months ago. After answering a few questions, I clicked the next SAVE & CONTINUE button and got the following:

The Please wait message remained for about 10 minutes before I gave up waiting. I then exited and restarted the application process. I again got the seemingly infinite Please wait message at the same step in the application. Each time I resume this application, I get an infinite Please wait message.

Under the hood, my web browser's console indicates that the client-side JavaScript threw an exception and stopped executing because data provided by Healthcare.gov wasn't formatted as expected by the Healthcare.gov software.

I still cannot complete this application. It seems I just need to continue to "Please wait" for CMS and QSSI to figure out how to create an online application that works.

Edit

20131117

Problem ID: 6540715378706480415
Entered by: Ben Simo

Healthcare.gov can't handle application edits

One of my Healthcare.gov application attempts has been stuck for two weeks. Each time I attempt to resume filling out the application, it prompts me to answer a couple questions and then gets stuck on a "Please wait" display. This message stays on the screen until the session times out.

Chrome's console shows me that there is an uncaught Javascript error that is preventing me from completing the application.

This error is occurring in code that appears to be attempting to retrieve the name of someone on my application.

A member.personName object in my application is null. The code is expecting that this contain elements named firstName and lastName and suffixName.

So, why does my application contain people filled with null values? Early in the application process, I was getting a similar error message. I deleted some people from my application using the provided user interface and was able to get further into the application process.

It appears that those deleted family members were removed from the application but the data structures in which their data was stored remain; filled with null values and empty arrays. It appears that the application is now getting stuck on those deleted family members.

And, now that I'm further into the application process, the options to add the deleted family members back into the application is no longer available.

Did the developers of Healthcare.gov not anticipate that someone might use the features they provide to remove people from an application? Did the testers not try entering and then later editing data entered into an application?

Although I don't really know what testing was or was not done, I can't help but think that no one strayed off the happiest of paths as they tested this.

Edit

20131103

Problem ID: 5526608595781939317
Entered by: Ben Simo

Healthcare.gov asks me to wait longer than it will wait for me

I've been waiting over a half hour. Should I keep waiting?

I eventually gave up. I then logged into the site fresh, and completed all the earlier steps in the form (it makes users mostly start over if there's an issue along the way), and waited again. I've not yet been able to get past this income verification step.

Edit

20110905

Problem ID: 6782646722055594014
Entered by: Ben Simo

Warning: This may take a few seconds

@lucianodinapoli tweets: most useful dialog box in the world

Warning, it may take you a few seconds to read this dialog, move your mouse, and click the OK button. This dialog is only a distraction to keep you entertained while we process your request.

Edit

20100328

Problem ID: 1135793819968187623
Entered by: Ben Simo

Please wait while we process your check(s)

@miceyj: soo umm I pulled up to the drive thru ATM & saw this..

Finding an ATM that appears to have taken so long processing the previous user's deposit that they gave up waiting and abandoned the machine gives me reason to not put much trust in the device.

At least it isn't displaying any information about the previous user or their account. However, if this processing ever does complete, will whomever comes across the machine have access to the previous user's account?

Edit

20100128

Problem ID: 6512968875276173226
Entered by: Ben Simo

Reboot to Save

After making updates to a document in Microsoft Word 2007, I press the Save button.

Configuring? I told it to save.

Seven minutes later, the Microsoft Office setup tells me I need to reboot to complete setup.

What about the changes I wanted to save? Were they saved? Saving should not require a reboot.

I click the No button. The Setup program starts up again.

Six minutes later, an error dialog appears.

Error 1719. What does that mean?

Contact my support personnel? That would be me.

I am not at all OK with having spent the last 13 minutes trying to save a document and getting nowhere -- but I click the OK button anyway. (Where's the "I'm frustrated and just want to make this error go away" button?)

I now stare at my screen -- uncertain if my document has been saved.

I press the Save button again. The Setup program launches... :(

Edit

20100123

Problem ID: 331197613513923239
Entered by: Ben Simo

Keep waiting?

@edfladung: great error messages from movable type, how 5 years ago is this?

An error occurred. Is the error that the user is performing a search? Or did an error occur in performing the search? Should the user keep waiting for an erroneous search to complete?

Edit

20100120

Problem ID: 6094243198307575241
Entered by: Ben Simo

Do not turn the power off

“Whyyyyyyy Wiiii, Whyyyy nowwwww do you want to do a system update!!! FAIL!” - @iRx

What happens if the power goes out?

Edit

20100117

Problem ID: 5736004940157221395
Entered by: Ben Simo

Lengthy operation in progress

“Hmmm, all i did was try and indent a line in Netbeans 6.8 (OSX Snowleopard) and I have been waiting for ages!” - @absolutehype

And what happens if you try something really complex? Something like cut and paste.

Edit

20091231

Problem ID: 3139063843505527385
Entered by: Ben Simo

Wait or select OK?

“Windows media center is grumpy today” - @antidale

Wait while files are added or select okay to continue using the system. Does pressing OK to continue cancel the adding of media files?

Edit

Problem ID: 2969416042625759636
Entered by: Ben Simo

Installing...

“No video game should take 10 minutes to install.” - @rbieber

Back in the '80s, I often waited 10 minutes for games to load from floppy disk. :)

Edit

20091229

Problem ID: 6914235075458660113
Entered by: Ben Simo

Windows doing whatever it wants to do

“Why does windows feel the urge2do whatever it wants to do? Its adobes fault ,they should make audition4mac” - @danmorris69

Edit

20091228

Problem ID: 6571054203295391887
Entered by: Ben Simo

Respond or be killed

“First error with Chromium.. it's awesome.” - @fynflood

I'm not sure what that thing is supposed to be, but it sure looks ill.

Edit

Usability Heuristics

• Visibility of system status Visibility of system status: The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.

• Match between system and the real world Match between system and the real world: The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.

• User control and freedom User control and freedom: Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.

• Consistency and standards Consistency and standards: Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.

• Error prevention Error prevention: Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.

• Recognition rather than recall Recognition rather than recall: Minimize the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.

• Flexibility and efficiency of use Flexibility and efficiency of use: Accelerators -- unseen by the novice user -- may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.

• Aesthetic and minimalist design Aesthetic and minimalist design: Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.

• Help users recognize, diagnose, and recover from errors Help users recognize, diagnose, and recover from errors: Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.

• Help and documentation Help and documentation: Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.

Consistency Heuristics

-F amiliar Familiar: The product is not consistent with the pattern of any familiar problem.

E xplainable Explainable: The product is explainable.

W orld World: The product is consistent with the real world.

H istory History: The present version of the product is consistent with past versions of it.

I mage Image: The product is consistent with an image that the organization wants to project.

C omparable Products Comparable Products: The product is consistent with comparable systems.

C laims Claims: The product is consistent with what important people say it’s supposed to be.

U ser Expectations User Expectations: The product is consistent with what users want.

P roduct Product: Each element of the product is consistent with comparable elements in the same system.

P urpose Purpose: The product is consistent with its purposes, both explicit and implicit.

S tatutes Statutes: The product is consistent with applicable laws.

FAILURE Heuristics

F unctional Functional: The error detecting, reporting, and handling functions properly.

A ppropriate Appropriate: Errors are reported at the appropriate time in an appropriate manner.

I mpact Impact: The impact of the failure is communicated to those impacted.

L og Log: The error is appropriately logged; or not logged.

U ser Interface User Interface: The error is reported in the user interface in terms that the user understands.

R ecovery Recovery: The user is informed of what they need to do to recover from the error.

E motions Emotions: The error handling and reporting has a positive influence on user emotions.

Security Vulnerabilities

1. Injection Injection: Injection flaws occur when untrusted data is sent to an interpreter as part of a command. The attacker’s hostile data can trick the interpreter into executing unintended commands or accessing data without authorization.

2. Broken authentication and session management Broken authentication and session management: Application functions related to authentication and session management are often not implemented correctly, allowing attackers to compromise passwords, keys, or session tokens, or to exploit other implementation flaws to assume other users’ identities.

3. Cross-Site Scripting Cross-Site Scripting (XSS): XSS flaws occur whenever an application takes untrusted data and sends it to a web browser without proper validation or escaping. XSS allows attackers to execute scripts in the victim’s browser which can hijack user sessions, deface web sites, or redirect the user to malicious sites.

4. Insecure Direct Object References Insecure Direct Object References: A direct object reference occurs when a developer exposes a reference to an internal implementation object, such as a file, directory, or database key. Without an access control check or other protection, attackers can manipulate these references to gain unauthorized access to data.

5. Security Misconfiguration Security Misconfiguration: Good security requires having a secure configuration defined and deployed for the application, frameworks, application server, web server, database server, and platform. Secure settings should be defined, implemented, and maintained, as defaults are often insecure. Additionally, software should be kept up to date.

6. Sensitive Data Exposure Sensitive Data Exposure: Many web applications do not properly protect sensitive data, such as credit cards, tax IDs, and authentication credentials. Attackers may steal or modify such weakly protected data to conduct credit card fraud, identity theft, or other crimes. Sensitive data deserves extra protection such as encryption at rest or in transit, as well as special precautions when exchanged with the browser.

7. Missing Function Level Access Control Missing Function Level Access Control: Most web applications verify function level access rights before making that functionality visible in the UI. However, applications need to perform the same access control checks on the server when each function is accessed. If requests are not verified, attackers will be able to forge requests in order to access functionality without proper authorization.

8. Cross-Site Request Forgery Cross-Site Request Forgery (CSRF): A CSRF attack forces a logged-on victim’s browser to send a forged HTTP request, including the victim’s session cookie and any other automatically included authentication information, to a vulnerable web application. This allows the attacker to force the victim’s browser to generate requests the vulnerable application thinks are legitimate requests from the victim.

9. Using Components with Known Vulnerabilities Using Components with Known Vulnerabilities: Running software components with known vulnerabilities can compromise the vulnerable components and anything those components can access -- undermining defenses.

10. Unvalidated Redirects and Forwards Unvalidated Redirects and Forwards: Using untrusted data, without validation, to determine the destination of redirects and forwards can enable attackers to redirect victims to phisihing or malware sites.

Is There A Problem Here?

20140122

Healthcare.gov still says "Please wait"

20131117

Healthcare.gov can't handle application edits

20131103

Healthcare.gov asks me to wait longer than it will wait for me

20110905

Warning: This may take a few seconds

20100328

Please wait while we process your check(s)

20100128

Reboot to Save

20100123

Keep waiting?

20100120

Do not turn the power off

20100117

Lengthy operation in progress

20091231

Wait or select OK?

Installing...

20091229

Windows doing whatever it wants to do

20091228

Respond or be killed

Problem or no problem?

Usability Heuristics

Consistency Heuristics

FAILURE Heuristics

Security Vulnerabilities

Popular

Recent Problems

Recent Comments