Axiell Quria Ideas

Welcome to the Ideas Portal for Quria users!
Axiell invites customers to contribute ideas for new features or functions. While we can't develop every suggestion, your input helps shape Quria’s roadmap. You are welcome to add ideas, vote on others’ suggestions, and discuss them. To make this portal more effective, please submit your ideas in English.

Ideas are regularly reviewed by the product manager or local representative. Once reviewed, the ideas are visible for voting and discussion. Popular ideas will be prioritized within our backlog.

Status meanings:

  • Under investigation: Developers and specialists are discussing if the idea is possible to implement.

  • Planned: The suggestion will be fulfilled in some way in a foreseeable future

  • Future consideration: A good idea, without technical obstacles, but it can't be prioritized into the roadmap at the moment.

  • No action: Technical or other issues prevent development, or an alternative solution exists.

We reserve the right to reject ideas and to close issues after 3 months if we don't receive answers to follow-up questions.

For technical issues, please contact your local support.

Notification of failed jobs

Manchmal schlagen geplante Jobs fehl.

In der Regel reicht es dann, den Job nochmal manuell zu starten.

Leider merkt man oft nicht, dass der Job fehlgeschlagen ist.

Dafür müsste man mindestens täglich nachschauen.

Es wäre sehr hilfreich, wenn eine automatische Benachrichtigung verschickt werden könnte, wenn bei einem Job ein Fehler auftritt.


Sometimes scheduled jobs fail.

It is usually sufficient to start the job again manually.

Unfortunately, you often don't realize that the job has failed.

You would have to check at least daily for that.

It would be very helpful if an automatic notification could be sent when a job encounters an error.

  • Andreas Klinger
  • Jan 20 2023
  • Resolved/not for implementation
  • Attach files
  • Admin
    Magdalena Olofsson (Axiell) commented
    14 Apr 07:41am

    This solution was implemented in April 2024:

    It is now possible to filter the list of logs on Aborted and Failed jobs. The difference is that Aborted jobs are due to e.g. a new release is deployed and running jobs have been aborted. They need to be started again to be finished, but there is no underlying problem. If specific jobs are continuously failing, please report to Axiell for investigation.

    Note: the Datetime column contains start datetime if the list is not filtered. If filtered on Aborted and/Or Failed, the stop datetime will be presented.

    The decision has been made that this solution is good enought and not notification service about failed jobs will be implemented and therefore this idea will be closed.