This issue is being looked into and we hope to have it working later today. Thank you for your reports.

Please see 's post for an update if you can't get to the ticket system. Staff also don't post ticket replies on the forums - we keep ticket-related things within the ticket system!

The link to the Ticket Center is here: https://subeta.net/tickets.php

Please go there and you can see all your open tickets, as well as links to open them up.

Appears to be working for me now! Please ping me if it isn't!

If you've tried to autoprice over the last few days and it broke... it's just autopricing your items a few times

All of the items are out of the queue, did it run for y'all, just relaly slowly?

I'm going to look into this today, I'm looking at the queue for the autopricer and I'm not seeing any active shops in it, and it's been run on more than 50 shops in the last few hours so it's working for some people, at least.

We see the reports and it's being looked into.

Thanks everyone, I'm taking a look now. We've pushed a lot of code changes in the last few day and the process that runs things in the background (like the autopricer) might have gotten out of date.

Yup, it's currently stuck in a queue. Should be running again in about fix minutes, and I've added this to the list of things to make sure that we monitor automatically for the new status page

And this is AFTER you got the alert confirming that autopricing finished?

Could you list some examples of specific items that fail to autoprice? Or it is always all the items in the shop that stay at 0 sP?

Do you get any errors or lag at the stage "sending prices to server" when this happens?

And when it fails, does the progress bar still show the correct number of items being priced, or does it show like "0 / 0 items priced" ?

We are experiencing some delays to the Autopricer tonight due to a coding error I made earlier. This happened about 2 hours ago. The error has been resolved now, and the Autopricer is just taking time working through the backed up queue. Your shops should finish autopricing shortly if they haven't yet.

I'm very sorry about this issue! I have made a modification to the code as an extra safeguard against this situation in the future. "^^

The same issue also caused delays in updating users online and delivering sidebar notifications. A bit off-topic on this thread but just mentioning since I'm pinging so many people for it

And so everyone is aware, we also discovered another glitch that the Autopricer will sometimes display incorrect numbers on the progress bar page. This is just a display error - the numbers are not accurate to what is actually being autopriced - and as far as I can tell it happens when autopricing multiple shops at the same time. This issue is now on our radar (and internal bug tracker!)

Hey everyone!

Something we anticipated but didn't put enough early work into was all of the excitement around pet names brought back some older users, and the combination of that and our new subscriptions (meaning a lot more gold accounts, meaning a lot more autopricing) meant that our autopricing queue got WAY behind overnight.

It's currently working through the queue items (there were over 4,000 this morning, which are events and shops needing queued) and you should have your shops priced.

We also added additional processing power to the queue workers, so this shouldn't happen again :D

The queue worker seems to be down - it looks like it went down about 2 hours (?) ago. Unfortunately I'm not able to solve this problem. will look into this when he's next online! Yes, autopricer and sidebar events both use this system so they are both affected by this issue.

(I am running the worker manually right now, so some of the backlog will be processed, but I won't be able to do this all night.)

Interesting - I'm working through them again now. Taking a closer look at what's causing it to get stuck repeatedly.

Oh dear, that's an older link we never updated. I'll see about making that more accurate.

Your autopricer is still working, and you will get a sidebar event when it is finished. There is a bit of a backlog right now it is working through.

Hey everyone, a quick little post-mortem and info on this issue. and I managed to figure out what the problem was with the worker. The issue was that one of our servers had an outdated configuration value. We had made some configuration changes this week and overlooked updating it in that one spot. This has now been resolved.

Some more info for you:

1. We've moved sidebar events to a separate queue from autopricer, so that an error within the autopricer queue no longer creates a large backlog of sidebar events.

2. We've added some extra error handling to the autopricer code so that it can recover more gracefully from more kinds of errors, instead of crashing.

3. The autopricer page has a few display errors; most notably the numbers it shows on the progress bar will be inaccurate if you are autopricing multiple shops at once. It may also be inaccurate if you navigate away from the page and navigate back. This is just a display error, so it is not accurately showing the number that was actually autopriced or in the queue. It is unfortunately not an easy fix but it is on our radar, and in the meantime I just wanted to say something so everyone is aware.

Thank you to everyone who helped out by reporting these issues here and in our Discord :)

We've just reset everyone's autopricer state - please try again now :)

If you need CSC reimbursed for your previous attempt please file a ticket for reimbursement.

Hey everyone; I managed to finally pinpoint the exact issue with it. Less clear is how to resolve the issue, but I just made a change that might help. Please let me know if it seems better or worse now, or if there's no noticeable change (still useful to know!)

Some of your shops were stuck in a "halfway" state with autopricing; I've manually reset these, so if you experienced issues earlier today, you can try again now with a clean slate.

By the way: When reporting autopricer, please specify which step of the autopricing had the problem. This helps us troubleshoot faster since it tells us exactly which step we need to look at first.