Bugs are an unavoidable part of any software product. The WeSpire engineering team fixes bugs as quickly as possible and relies on user reports to help them find and diagnose application errors. When you encounter a bug, please share as clearly as possible. The clearer your ticket, the fastest fix.
Do you have an idea that would make your WeSpire experience better and we want to hear them. Submit your feature request (or one you've heard from one of your Users) and we'll add your notes to existing product wishes or create new ones.
When you encounter a bug or an error page, the first thing you should do is refresh the page and try again. This fixes ~50% of reported problems. If the problem persists, then you have a real bug on your hands and we'll need your help to get it fixed.
Sometimes a bug results in an error page. Our most common error pages are described below.
This error page appears when you're following a link and arriving at a WeSpire Activity that your user account doesn't have access to. This could be because the thing belongs to another brand, filtered to a team you're not on, soft deleted, or not published yet. We don't yet provide much in the way of detail about why you can't access a thing, but this is likely what you'll see.
Try these steps before reaching out to Support:
Donation accounts are enabled on a per-user basis. The eligibility of who has access to donation features differs between customers. The general policies are set up in the implementation phase but there are sometimes edge cases or delays in the eligibility process (new employees might not be eligible for a certain period, for example).
This error happens whenever a user without a donation account visits a Donation page. Users who think they should have access to donation accounts should submit a support ticket.
You can reduce the incidence of this error by ensuring that your HR file is sent to WeSpire regularly and lists all employees who should be eligible.
Maybe your WiFi went out. Maybe there was a random, unexpected server error. Something went very haywire that we did not expect (and may be out of our control), and that's when/why you'd see this message.
Users should dismiss it and try their operation again. If the error re-occurs, they should submit a support ticket.
