Axsys Signals Troubleshooting
What you see, what it means, what to do
Version
0.4
Date
2026-09-14
Audience
Anyone who is stuck
1.How to use this page
Something on your screen stopped you. Find the exact words you see in the What you see column of the tables below. The next column says what it means. The last column says what to do.
Each table covers one area: signing in, inside the workspace, invitations, email that did not arrive, the page looking wrong. If you cannot find your words, go to section 7.
When something breaks on our side, the page carries a short reference code, printed under the message as "Reference:" and twelve letters and numbers. The "Something went wrong" pages and the "One moment" page both have it; the plain notices, like "Link expired", do not, because nothing went wrong to look up. Quote the code to us with the exact words on the screen. It is the fastest way for us to find your case in our log.
Some things to know before you read the tables:
- The address is https://signals.srv1195619.hstgr.cloud. Sign in at https://signals.srv1195619.hstgr.cloud/login.
- You sign in with your email and your Axsys password. If you also use the Axsys CRM, it is the same password.
- Access is by invitation only. There is no sign up page.
- The public status page is https://signals.srv1195619.hstgr.cloud/status. It needs no sign in. Check it first when anything says "One moment" or "Delayed".
- This page lives at https://signals.srv1195619.hstgr.cloud/help/troubleshooting and needs no sign in. The sign in page links here under "Stuck? Help with signing in", and every message page has a "Help" link at the bottom.
- This page is version 0.4, updated 2026-09-14. It is rebuilt with every release.
2.Signing in
Every row quotes the real words the app shows today. Where the words are about to change, the row says so.
| What you see | What it means | What to do |
|---|---|---|
| Sign in with the lines "New here? Access comes by invitation from your workspace admin. Already have an Axsys account? Sign in with that email and password." and "Stuck? Help with signing in" | This is the normal sign in page. The lines are not errors. There is no sign up form. Access comes by invitation only. An Axsys account from the CRM works here with the same email and password. | Type your email and your Axsys password. If you have an invitation email, open the link in that email instead of this page. "Help with signing in" brings you here. |
| Wrong email or password. | The email and password did not match an account. Either can be the problem. The app does not say which one, on purpose, so nobody can use this page to check whether an email has an account. | Check the spelling of your email. Check caps lock. Your password is your Axsys password, the same one as the CRM if you use it. If you have never set a password (for example you only ever signed in to the CRM with Microsoft), click "Forgot your password?" and set one. Stop after a few tries: ten wrong tries lock the email. |
| Too many attempts. Wait up to an hour and try again, or reset your password, which clears the wait. | You are locked. Ten tries on one email inside an hour, right or wrong, lock that email for up to an hour. Ten tries from one network address inside fifteen minutes lock that address for fifteen minutes. Every try counts, even ones made while our data provider was down. Older screenshots show the shorter "Too many attempts. Try again later." on this page; it was reworded on 2026-09-04. | Wait. The lock ends by itself within an hour. If you cannot wait, click "Forgot your password?": setting a new password from the email link clears both locks, the one on your email and the one on your network address, and signs you in straight away. |
| We cannot reach the sign-in service right now. Your account is fine. Please try again in a few minutes. | Our data provider did not answer. Nothing is wrong with your account or your password. | Open https://signals.srv1195619.hstgr.cloud/status. If it says "Delayed", wait a few minutes and try again. Do not keep pressing Sign in: each press counts toward the ten. |
| Check your email with "If that account exists, a reset link is on its way." | You asked for a password reset. The app always shows this, even when the email has no account and even when you asked too often (three times an hour per email, five times an hour per network address). This is on purpose, so nobody can use the form to find out which emails have accounts. | Look for an email from no-reply@axsys.ai with the subject "Reset your Axsys Signals password". Check spam. The link works for one hour. If nothing arrives in ten minutes, see section 5. |
| Try again shortly with "We cannot send reset emails right now. Your account is fine. Please try again in a few minutes." | Our data provider did not answer when you asked for a reset. No email was sent. | Open https://signals.srv1195619.hstgr.cloud/status, wait a few minutes, ask for the reset again. |
| Link expired with "That reset link is no longer valid. Request a new one." | The reset link is older than one hour, or it was already used, or the password changed after it was sent (a reset link is tied to the password you had when you asked), or the link was cut in half by your email program. | Go to https://signals.srv1195619.hstgr.cloud/forgot and ask for a new link. Open the newest email. Copy the whole link if clicking does not work. |
| Link expired with "That reset link is no longer valid." | Same as above, shown when you pressed Set password on a link that had already gone stale. | Ask for a new link at https://signals.srv1195619.hstgr.cloud/forgot. |
| Choose a new password with "New password (at least 10 characters)" | The reset link worked. This is the form. | Type a password of ten or more characters and press Set password. You are signed in right after. |
| Use at least 10 characters. | The password you typed is shorter than ten characters. The CRM accepts eight; Signals needs ten. The same password serves both, so pick ten or more. | Type a longer password. |
| Something went wrong with "Try the link again in a minute." | Saving your new password, or creating your account, did not go through at our data provider. Nothing was changed. | Wait a minute and open the same link again. If it happens twice, check https://signals.srv1195619.hstgr.cloud/status, then see section 7. |
| Slow down with "Too many attempts. Try again later." | You pressed Set password (or Join workspace) more than ten times in an hour from one network address. | Wait up to an hour, then try once. |
| Signed in as someone else with "This invitation is for a different email address. Sign out and open the link again." | You are signed in as one email, and the invitation was sent to another. An invitation only works for the email it was sent to. | Click Sign out, then open the invitation link again. If the invitation went to the wrong address, ask your workspace admin to invite the right one. |
| This email has no password yet with "Set one with Reset password, then open this invitation link again." | Your email has an Axsys account with no password. This happens when you only ever signed in to the CRM with Microsoft. There is no Microsoft sign in on Signals, so the account needs a password first. Before 2026-09-04 this page was titled Use Microsoft sign-in and said "This email signs in with Microsoft on the internal dashboard. Ask Axsys to link it." That text pointed at a sign in that does not exist here and was replaced. | Click "Reset password" (it goes to https://signals.srv1195619.hstgr.cloud/forgot), set a password by email, then open the invitation link again and join with that password. You do not need to ask Axsys to link anything. |
| No workspace yet with "Your account is not in a workspace. Ask your admin for an invitation. If you have an invitation email, open its link now; the sign in you just did stays valid." | Your sign in worked, but your account is not a member of any workspace. Common causes: you created an account on the CRM, or you reset your password, before accepting an invitation. | If you have an invitation email, open the link in it; accepting adds you to the workspace, and you stay signed in. If you have none, ask your workspace admin to invite you. Signing in again will not change this. |
| Choose a workspace with a list of names | You belong to more than one workspace, and the address did not say which one you want. Not an error. | Click the workspace you want. The address then carries the workspace name, so you can bookmark it. |
| Almost there with "The workspace pages are not installed on this server yet. The API is live at /app/api/dataset." | A deployment problem on our side. The server is missing its page files. Nothing you did caused it. | Tell us (section 7). There is nothing to fix on your side. |
| Email verified with "You are all set. Open the workspace." | You clicked a verification link and it worked. | Click "Open the workspace". |
| Link expired with "That verification link is no longer valid." | A verification link is older than seven days, or the email on the account changed. Today nothing in the app requires a verified email, so this blocks nothing. | Ignore it and sign in as usual. |
| Not found with "No such page." | The address is wrong, or the page moved. | Check the address bar. Start again from https://signals.srv1195619.hstgr.cloud/app. |
| One moment with "We are having a brief hiccup reaching your data. Nothing is lost and nothing needs fixing on your side. Please try again in a minute." | Our data provider did not answer in time. Your data is safe. | Wait a minute and click "Try again". Check https://signals.srv1195619.hstgr.cloud/status. If it keeps happening for more than fifteen minutes, tell your workspace admin or see section 7. |
| Status page saying "Sign-in and data: Delayed" | Our data provider is slow or not answering. Signed in pages keep showing your last good data with a note at the top. Signing in may not work until it recovers. | Wait. Nothing is lost. Try again in a few minutes. |
| Status page saying "Sign-in and data: Normal" but you still cannot sign in | The service is up, so the problem is on the sign in form itself. | Go back through the rows above: wrong password, locked, no password yet, or no workspace. |
| You are sent back to the Sign in page while working | Your session ended. A session ends after thirty days without use, ninety days after you first signed in, when you sign out in another tab, or when you reset your password (a reset signs out every other session on purpose). | Sign in again. |
3.Inside the workspace
Once you are in, most problems show as a short message in a box at the bottom of the screen (it goes away after a few seconds), a red box inside a panel, or an amber band across the top of the page. Some messages are plain sentences. Some are short codes in lower case with underscores, like store_unavailable. The codes are being turned into sentences one at a time; the rows below tell you what each one means today.
| What you see | What it means | What to do |
|---|---|---|
| Amber band Live data delayed: "Live data is delayed. You are seeing the last good copy from (date and time). Nothing is lost. Refresh in a minute or two to check again." | The page normally rebuilds its data every 60 minutes. The last rebuild failed because our data provider did not answer, so the page shows the last good copy it kept, in memory or on disk. It tries the provider again at most once a minute. | Keep working. Refresh in a minute or two. Check https://signals.srv1195619.hstgr.cloud/status if the band stays for a long time. |
| Amber band Note from the team | We wrote a note during an incident or a planned change. It is not an error. | Read it. Nothing else to do. |
| Amber band One moment with the hiccup sentence, and an empty sidebar | The page could not load your name and workspace because our data provider did not answer. | Refresh in a minute. Check https://signals.srv1195619.hstgr.cloud/status. |
"We are having a brief hiccup reaching your data. Nothing is lost and nothing needs fixing on your side. Please try again in a minute." in a box or a red panel (temporarily_unavailable) | One request failed because of the provider. Whatever you were saving was not saved. | Wait a minute and do it again. |
store_unavailable | Our data provider did not answer or refused the request. Nothing was saved. | Wait a minute and try again. Check https://signals.srv1195619.hstgr.cloud/status. |
not_signed_in (you usually do not see this; the page sends you to Sign in instead) | Your session ended. | Sign in again. See the last row of section 2. |
choose_workspace, or the sidebar stays empty and panels show choose_workspace | You belong to more than one workspace and this address did not say which one. | Go to https://signals.srv1195619.hstgr.cloud/app and click the workspace you want. Use the address it gives you from then on. |
no_workspace | You are no longer a member of any workspace. An admin removed you, or you never accepted an invitation. | Ask your workspace admin for an invitation. |
"This workspace is read-only. Contact Axsys to continue." (trial_expired), and Read only under the workspace name in the sidebar | The workspace's trial has ended, or Axsys set it to read only. You can still read everything. Saving, rating, inviting and role changes are off. | Contact the person who invited you, or the Axsys team at jonathan.bayo@axsys.ai to continue. |
| Trial · (number) days left under the workspace name | How many days are left in the trial. Not an error. Trials are set by Axsys, thirty days by default. | Nothing. Contact the person who invited you, or the Axsys team at jonathan.bayo@axsys.ai before it ends if you want to keep going. |
forbidden | Your role does not allow that action. Admins manage people, settings, the ICP and the source switches; Contributors rate signals, shape the set and switch kinds of event on or off; Viewers read. If you expect a button and it is not there, that is your role, not a mistake. | Ask a workspace admin to do it, or to change your role on the Team page. |
| "Only the gold-standard owner, or an admin passing confirm true, can transfer it." | Only the gold owner (the one account that can never be removed without a handover) can hand that role to someone else. | Ask the gold owner. |
| "Only the gold-standard owner can mark gold signals." | Marking a signal as gold is reserved for the gold owner. | Ask the gold owner. |
| "That is the last admin; promote someone else first." or "Every workspace needs at least one admin." | You tried to demote or remove the only admin. | Make someone else an admin first, then try again. |
| "The gold owner needs a handover first." or "Transfer the gold-standard owner role first." | You tried to remove the gold owner. | Transfer the gold owner role to someone else first. |
| "That person is already a member." | The email you tried to invite is already in this workspace. | Nothing to do. Change their role on the Team page if that is what you wanted. |
"Slow down a little." on the Signal desk, on a lead vote, on Send to CRM, on Sources, in Report a problem, in Ask Signals, or slow_down elsewhere | You hit a rate cap. Ratings, notes and lead votes: 240 an hour per person. Sending leads to a CRM, tests included: 60 an hour for the whole workspace. Adding a source, importing a CSV or applying a starter set: 60 an hour for the whole workspace, all three together, and a whole file counts as one. Report a problem: 10 an hour per person. Ask Signals: 20 questions an hour per person, and 60 a day for the whole workspace. Verification emails: three an hour. | Wait a little, then continue. Nothing you did was lost except the last click. |
policy with a detail such as "table not allowed" or "column not readable: (name)" | The page asked for data it is not allowed to read. That means a bug in the page, or an address that was edited by hand. | Reload the page. If it comes back, send us the address and the words (section 7). |
internal | The old catch all error. It has been replaced by the "One moment" page and the hiccup sentence. You should not see it any more. | If you do, send us the address and the time (section 7). |
| Not available right now under the Library title | The library could not be loaded from our data provider. | Reload in a minute. Check https://signals.srv1195619.hstgr.cloud/status. |
| "Saved for the Axsys team's weekly review. Nothing in the scoring changes by itself." after rating on the Signal desk, and the footer "your ratings are saved for the Axsys team's weekly review · nothing in the scoring changes by itself" | Exactly what it says. Your rating and note are stored, shared with your team, and reviewed by the Axsys team. Nothing in the scoring changes by itself. Before 2026-09-04 these pages said "Saved. That trains the scoring.", "ratings and notes feed back into scoring" and "your notes train the model"; those sentences overstated it and were replaced. | Keep rating. It is read by people, not by the scorer, until we say otherwise. |
| The Status column on the Signal desk reads Last result (a date), or No results yet | That is the date of the newest result of that kind in your workspace. It is green only when the date is inside seven days. It says what your results look like, not whether a collector ran. Before 2026-09-05 this column read "Live in sample" on every row, which was a fixed word and not a measurement. | Nothing to fix. To find out whether the collector behind it ran, open the Health page in the rail. |
| Almost ready with "Your admin is setting up who you sell to. The queue opens when that is approved." and links to Team and Guide | Your workspace has the setup gate on and no approved ICP yet. Only a workspace admin can finish the setup. You are not locked out of Team, Guide, Manual or Troubleshooting. Not an error. | Ask your workspace admin to open https://signals.srv1195619.hstgr.cloud/app/icp/setup and approve the profile. Nothing to fix on your side. |
| You are an admin, you open the queue, and you land on Set up who you sell to at /app/icp/setup instead | Your workspace has the setup gate on and no approved ICP yet. Every app page sends an admin here until one is approved. | Answer the one question (paste your profile, or answer the six questions), check the review screen, press Approve. The queue opens right after. |
| Under the Approve button, a list of short lines such as an industry not on the list, a smallest size bigger than the largest, a pattern that does not work, or a sentence or answer that is too long | The server checked the profile before saving and found something it cannot use. Nothing was saved. The lines name each problem. | Fix each line it names (pick an industry from the list, make the smallest size less than the largest, shorten the text) and press Approve again. |
| No ICP yet. Your workspace admin sets it on the ICP page. on the ICP page, with No attributes yet. or No targeting rules yet. | No profile has been approved for this workspace yet, or no targeting rules exist. Not an error. | An admin sets it: open https://signals.srv1195619.hstgr.cloud/app/icp/setup, or press Edit on the ICP page. Contributors and viewers ask their admin. |
| Ownership: recorded, not yet enforced on the ICP page, and Triggers or Buyer roles shown without a filter | Exactly what it says. Ownership, triggers and buyer roles are stored and shown, and do not change the queue yet, because no company record carries ownership today. | Nothing to do. The industries, size band, locations and exclusions are the filters that work now. |
| The switches on Your signals are grey and will not move, with the line "Your admin or a contributor sets these" | Your role is Viewer, so the switches are read only for you. Not an error. The same happens for everyone when the workspace is read only (Read only under the workspace name: the trial ended). | Ask an admin or a contributor to flip it, or ask your admin to change your role on the Team page. If the workspace is read only, contact the person who invited you, or the Axsys team at jonathan.bayo@axsys.ai. |
| A switch on Sources will not move, or is grey with the note "Only an admin can change this." | Only a workspace admin can switch a source channel on or off. Contributors and viewers see the switches disabled. Not an error. The same happens for everyone when the workspace is read only (Read only under the workspace name: the trial ended). | Ask a workspace admin to flip it, or ask your admin to change your role on the Team page. If the workspace is read only, contact the person who invited you, or the Axsys team at jonathan.bayo@axsys.ai. If you are an admin and it still will not move, reload the page and try once; if it snaps back with a message, the message says why. |
| A band on Your signals saying "Your profile is saved. Now choose what the desk watches; everything is on to start." with a Skip to your queue link | You just approved the profile on the setup screen and landed here. Not an error. Every kind of event is on. | Switch off what you do not want counted, or click Skip to your queue and come back later. |
| You switched a kind of event off on Your signals, or a channel off on Sources, and it still shows on Today or the desk | The queue is rebuilt on the next page load after a flip, and a rebuild can take up to a minute. | Wait a moment and refresh. If it is still there after a few minutes, check https://signals.srv1195619.hstgr.cloud/status, then see section 7. |
| An Off chip on a dim row in the Signal desk's source library | Someone in your workspace switched that kind of event off on Your signals, so its results do not count for your queue. Nothing is deleted. | Nothing, unless you want it back: click Manage on Your signals in the card header and switch it on. Admins and contributors only. |
| Send to CRM is grey, with the note "No webhook set. An admin sets it on the Team page.", or, if you are an admin, "No webhook set. Set your CRM webhook on the Team page." with a link | Nobody in your workspace has saved a CRM address yet, so there is nowhere to send a lead. The reason is printed as a line under the button, not only when you hover, so it reads the same on a phone and in a screen reader. Download CSV and Download JSON still work. | An admin opens the Team page, pastes the webhook address their CRM gave them into Workspace settings and presses Save. If you are not an admin, ask one. |
| You are a Viewer and there is no Send to CRM, no Good lead and no Bad lead | Viewers read, download and see the tallies. Sending a lead and voting belong to contributors and admins. Not an error. | Use Download CSV or Download JSON, or ask a teammate. Your admin can change your role on the Team page. |
| You look for Discovery or Workshop in the menu and cannot find them | They were taken out of the menu on 2026-09-04, on purpose. They are optional deep discovery, off the main path, and nothing in your queue depends on them. The pages still open at https://signals.srv1195619.hstgr.cloud/app/discovery and https://signals.srv1195619.hstgr.cloud/app/workshop; Discovery now says "This is the optional, in depth questionnaire behind the Axsys method. It is not required, and nothing in your queue depends on it. Who you sell to is set on the ICP page." and the Workshop says "Optional: where your answers to the deep questionnaire meet the desk's drafts. Not required for the queue." | Nothing is required of you there. Use the addresses above if you want them. |
| "This questionnaire has been finalized." on Discovery | An admin closed that questionnaire run, so its answers are locked. | Nothing to do. It does not affect the queue or the ICP page. |
| On the ICP page, one line: Your admin keeps the ICP private. and no ICP item in the rail | Your workspace admin switched off "Members can see the ICP" on the Team page. It is a choice, not an error, and only admins can read the document while it is off. Your queue is filtered by that ICP exactly as before; nothing about your accounts or your scores changes. | Ask your admin if you need to read it. One switch on the Team page turns it back on. |
| On the Health page, Health needs the n8n key on the server. and no rows | Health reads our automation server to find out whether each collector ran. This copy of the app was not given the key for it. Nothing is wrong with your workspace, your sources or your queue, and no other page is affected. | Tell the person who invited you, or the Axsys team at jonathan.bayo@axsys.ai. Only the Axsys team can add the key, and the page fills in by itself once it is there. |
| On the Health page, Health could not reach n8n right now. | Our automation server did not answer this time. The answer is normally cached for five minutes, so a reload straight away may show the same thing. | Wait a few minutes and reload. If it lasts more than an hour, see section 7. |
| A Health row says It did not run in this window for 1 day, but the same row looks fine on 7 days | Some collectors run once a week, not every day. Not a fault. | Widen the window with the 7 days or 30 days chip. |
| On the Health page, under the chips: The run history only goes back 14 days, so this window shows the last 14 days, not 30 days. | You pressed 30 days, and our automation server only keeps about a fortnight of run history. The page counts what it can really see and tells you so, rather than calling a fortnight a month. Not a fault. | Nothing to fix. Read the numbers as the shorter window the line names. |
| A Health row says This one is not collecting yet, so nothing from it has reached you. | That collector has never collected anything, so no result of its kind has ever reached your workspace. It is ours, not yours. The Sources page says the same thing on the channel it belongs to. | Nothing to fix on your side. Tell the person who invited you, or the Axsys team at jonathan.bayo@axsys.ai if it matters to you and we will say where it stands. |
| A Health row says We mostly use this one to fill in the numbers on your accounts. Very few of its finds reach your queue as results. | That one runs in the background to fill in facts such as revenue and ratios on an account. It is not there to put results in your queue, so an empty result count is the normal state. | Nothing to fix. |
| A Health row says We load this one by hand rather than on a schedule, so there is nothing to watch here yet. | No automation runs behind that row; we load it in batches. There is no run history to show. | Nothing to fix. Sources is where you see what it found. |
| Under the Webhook url field on the Team page, a red line such as "The address must start with https://.", "The host name needs a dot in it, like hooks.example.com.", "Use a host name, not an IP address.", "Take the user name and password out of the address.", "That host name does not resolve. Check the spelling.", "That address points inside a private network, not a CRM." or "That address points back at Axsys. Use your CRM address." | The address did not pass the check the app runs before it saves anything. Nothing was saved, and an address you already had is untouched. The rules: https only; a real host name with a dot, not a number address; no user name or password inside the address; and the name must not point at a local machine, at a private network, or back at Axsys. The name is looked up when you save, and again before every send. | Paste the address your CRM tool gave you, whole, with nothing before the https. If your CRM only offers an address inside your own network, it cannot be reached from here: ask your CRM person for one on the public internet, or use Download JSON instead. |
| The push failed: (a reason). Nothing is queued; try again. after Send to CRM | The lead did not reach your CRM. The reason is what your CRM answered, or that nothing answered inside eight seconds. There is no retry: nothing is saved for later and nothing runs in the night. | Read the reason. "404" or "410" means the address is wrong or was made again, so an admin saves the new one. "401" or "403" means your CRM refused us, usually a key or a paused trigger on their side. "no answer" means the tool behind the address is off or slow. Fix that, then press Send to CRM again; the lead is still on the brief. |
| The test failed with (a status): (a reason) after pressing Test on the Team page | The webhook address saved fine but the tool behind it did not accept our test message. The address and the secret are still stored. | Check with your CRM person that the trigger or Zap is turned on and that the address is the current one. Then press Test again. If the test works and a real lead still fails, ask them whether the tool caps the message size. |
| After a CSV import, N added, M rejected, with lines such as "row 7: url: the address must start with http or https", "row 12: duplicate of row 4", "row 15: already in your workspace", "row 501: over the cap", or "file: missing column" | Every rejected row is named with its number and the reason. The good rows went in; only the named ones did not. A reason that starts with "file:" means the whole file was refused, almost always a header row without name and url in it. The cap is 500 data rows per file. | Fix the named rows in your spreadsheet and import again. Importing the same file twice is safe: what is already in is skipped as "already in your workspace". Never put a password in the file; there is no column for one, and a source behind a login is marked with behind_login and described in login_note instead. |
| A source you added says Queued, not collected yet and never gets results | That is the honest state, not a fault. A source you add is written down and read by nothing until the Axsys team wires a collector to it, one source at a time. | Nothing to do. If it matters to your workspace, say so through Report a problem or to the person who invited you, or the Axsys team at jonathan.bayo@axsys.ai so it is put in front of the queue. |
| The tour never started, or you want it again | It starts by itself once for each person in each browser, the first time they open Today. It also waits when your workspace has no approved ICP yet, because there is no queue to point at, and it does not start by itself again once you have pressed Done or Skip. | Press Take the tour at the top right of any signed in page, or pick the same words from the Help menu beside it. Every step is on Today, so from another page Today opens with the tour running. The round ? that used to sit in the bottom right corner is gone; both buttons are at the top now. |
| Report a problem did not answer Sent. Reviewed on Thursdays. | The report did not reach us. "Slow down a little" means you passed ten reports in an hour. Anything else means our data provider did not take the row. | Copy your words before you close the box. If it said slow down, wait. Otherwise wait a minute and press Send again, or write the same words to the person who invited you, or the Axsys team at jonathan.bayo@axsys.ai. Reports are read on Thursdays, so nobody is waiting on this minute. |
| Slow down a little. in the Ask Signals panel | You asked more than twenty questions in one hour. That cap is per person, and it is there so one person cannot use up the workspace's day. | Wait a while, then ask again. The conversation in the panel is still there, and the pages themselves keep working. |
| This workspace has used its questions for today. in the Ask Signals panel | Everyone in the workspace together has asked sixty questions in the last day, which is the daily cap for the whole workspace. The count clears as the day rolls over. | Wait until tomorrow. Everything the panel reads is also on Today, the brief, Sources, Your signals, Health and the Library, so nothing is out of reach in the meantime. If your team needs more, ask the person who invited you, or the Axsys team at jonathan.bayo@axsys.ai. |
| Ask Signals is not available right now. in the panel, or no Ask Signals choice in the Help menu | The model that writes the answers could not be reached, or the server has no key for it. Nothing else in the app is affected, and nothing was changed, because the panel only reads. | Try again in a few minutes. If the choice is missing from the Help menu altogether, it is switched off on the server; ask the person who invited you, or the Axsys team at jonathan.bayo@axsys.ai if you expected it. |
| Something went wrong in the Ask Signals panel | The answer did not come back. The rest of the conversation is still in the panel, and nothing was changed, because the panel only reads. | Ask again in a minute. If it keeps happening, send the question and the time through Report a problem, or write to the person who invited you, or the Axsys team at jonathan.bayo@axsys.ai. |
| No results in the window yet., No votes yet, No chain rows yet., No members yet., No pending invites. | Empty states. There is simply nothing to show yet. | Nothing to fix. |
4.Invitations
An invitation is an email with a link. The link works for 14 days, for one email address, one time. A workspace admin sends it from the Team page.
| What you see | What it means | What to do |
|---|---|---|
| Email with the subject "You are invited to (workspace) on Axsys Signals" and the line "Accept the invitation (the link is valid for 14 days)." | Your invitation. It comes in two versions. A new account is told "You will pick a password when you accept." An existing Axsys account is told "You already have an Axsys account, so sign in with that email and password when you accept. Forgot it? Reset it on the sign in page, then open this link again." Invitations sent before 2026-09-04 carried only the first line, so an existing user may have been surprised by the password question on the page. | Click the link within 14 days. Do what your version of the email says. |
| Join (workspace) with "You were invited as (email). Create your account to get started." | You have no Axsys account yet. This page creates one. | Type your name and a password of ten or more characters, then click "Create account and join". |
| Join (workspace) with "You were invited as (email). You already have an Axsys account with this email, so confirm that password to join. There is no Microsoft sign-in here; the account is its own." | You already have an Axsys account (for example on the CRM). Confirm its password to join this workspace. | Type your Axsys password and click "Join workspace". The line "Don't remember it? Reset it here, then come back to this invite link." does what it says: reset by email, then open the same invitation link again. |
| Wrong password. on the Join page | The password does not match your existing Axsys account. | Try again, or use "Reset it here", then come back to the invitation link. |
| "Give your name and a password of at least 10 characters." | The name was empty or the password was shorter than ten characters. | Fill both and try again. |
| Invitation not valid with "This invitation link has expired or was withdrawn. Ask your workspace admin for a new one." | The link is older than 14 days, or an admin withdrew it, or it was already used, or a newer invitation was sent to the same email. Sending a new invitation always kills the older link, on purpose, so only one live link exists per email. A link cut in half by your email program looks the same. | Use the newest invitation email. If you already accepted once, just sign in at https://signals.srv1195619.hstgr.cloud/login. Otherwise ask your admin to send a new one. |
| Invitation not valid with "This invitation link has expired or was withdrawn." | Same as above, but it happened at the moment you pressed Join. Most often the link expired while the page was open, or someone withdrew it. | Ask your admin for a new invitation. |
| Signed in as someone else | You are signed in with a different email than the one invited. | Sign out and open the link again. If the invitation went to the wrong address, ask the admin to invite the right one. Invitations cannot be moved to another email. |
| This email has no password yet (before 2026-09-04: Use Microsoft sign-in) | Your email has an account with no password, usually because you only ever signed in to the CRM with Microsoft. | Click "Reset password", set one by email, then open the invitation link again. See the row in section 2. |
| Slow down | More than ten Join attempts in an hour from your network address. | Wait up to an hour. |
| On the Team page: "Invite emailed to (email)." | The invitation went out by email. | Tell the person to check their inbox and spam. |
| On the Team page: "Invite created. Email did not go out from here, so share this link:" followed by a link | Our mail did not send, but the invitation exists and the link is valid for 14 days. | Copy the link and send it to the person yourself. It shows as "link shared by hand" in Pending invites. |
| On the Team page, Pending invites, "expires (date)" | When that link stops working. | Send a new invitation after that date if they did not accept. |
| "Invite revoked" | You withdrew the link. It no longer works. | Send a new one if you need to. |
5.Email did not arrive
All mail from Signals comes from no-reply@axsys.ai. Three kinds exist.
| What you see | What it means | What to do |
|---|---|---|
| No reset email after "Check your email" | The reset mail has the subject "Reset your Axsys Signals password" and the link inside lasts one hour. It is only sent when the email has an account. The form says "Check your email" either way, on purpose. Only three requests an hour per email are sent; the rest are silently dropped. | Wait ten minutes. Check spam, junk and any company quarantine. Search for no-reply@axsys.ai. Make sure you typed the email your admin invited; the Team page shows it to your admin. Then ask once more. |
| No invitation email | The invitation mail has the subject "You are invited to (workspace) on Axsys Signals" and the link lasts 14 days. On the Team page your admin sees "emailed" or "link shared by hand" next to your name; if mail did not go out, the admin was given the link to share by hand. | Check spam and quarantine. Ask your admin to look at Pending invites and either copy you the link or send a new invitation (the new one kills the old link, so use the newest). |
| No verification email | Subject "Verify your email for Axsys Signals", link valid for seven days, three sends an hour. Nothing in the app requires it today. | Ignore it. It blocks nothing. |
| Company mail blocks it | Some company mail systems hold mail from new senders. | Ask your IT team to allow no-reply@axsys.ai. |
| The link in the email does not open | Some email programs cut long links in two. | Copy the whole link and paste it into the address bar. |
6.The page looks wrong
| What you see | What it means | What to do |
|---|---|---|
| The letters look plain or different from usual | The app uses three fonts from Google Fonts (Libre Franklin, Chivo Mono, Besley). If your network blocks fonts.googleapis.com or fonts.gstatic.com, your system font is used instead. Everything still works. This fallback is on purpose. The sign in and message pages load the same Libre Franklin as every other page. | Nothing to fix. Ask IT to allow the two font hosts if you want the real fonts. |
| The page is dark, or went back to light | There is a "Dark mode" or "Light mode" link under your name at the bottom of the sidebar. Your choice is remembered in this browser only. Another browser or a cleared browser starts light. The sign in and message pages are always light today. | Click the link to switch. |
| Things overlap or run off the edge on a phone or a narrow window | Every signed in page fits a phone as narrow as 390 pixels: the sidebar becomes a strip across the top, the tiles go two to a line, and a wide table scrolls inside its own box rather than pushing the page sideways. So this should not happen. If it does, it is a fault and we want to know. | Reload the page first. If it is still wrong, send us the things listed in section 7, and say which phone and browser you are on. |
| A blank page, or the sidebar never fills in | The app needs JavaScript and same site cookies. A blocker, a privacy extension or a corporate proxy that strips them stops the page. | Allow JavaScript and cookies for https://signals.srv1195619.hstgr.cloud. Try a private window with extensions off. |
| Numbers or dates seem a step behind | The page rebuilds its data every 60 minutes, and the status page shows times in UTC. | Refresh after a few minutes. |
| Supported browsers | Current Chrome, Edge, Safari and Firefox, on a desktop and on a phone. Older browsers are not tested. | Update your browser. |
7.Still stuck
Write to the person who invited you, or the Axsys team at jonathan.bayo@axsys.ai. Your workspace admin can also help with invitations and roles, because they see the Team page. Every message page (the ones with a title like "Link expired" or "No workspace yet") has a "Help" link at the bottom that brings you back here.
Tell us these things:
- The address bar. Copy the whole address.
- The exact words on the screen. A screenshot is best.
- The reference code under the message, if the page had one (section 1).
- The time it happened, with your time zone.
- The email you signed in with, or tried to.
Before you write, look at https://signals.srv1195619.hstgr.cloud/status. If it says "Delayed", the cause is on our side and we already know; wait a few minutes and try again. If it says "Normal" and you are still stuck, write to us.
"I did everything on this page and it still does not work."
Then it is ours to fix, not yours. Send the list above and we will take it from there.