> For the complete documentation index, see [llms.txt](https://docs.itconductor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itconductor.com/user-guide/flux/troubleshooting-guide/jobs-running-error.md).
# ‘Export/Import Jobs Still Running’ Error
### **Symptom**
The following messages are displayed when trying to submit a configuration for exporting or importing when there’s currently a different configuration in process
*‘Export Jobs Still Running. Currently selected Export Configuration cannot be executed’*
*‘Import Jobs Still Running. Currently selected Export Configuration cannot be executed’*
*‘Import Jobs Still Running. Currently selected Import Configuration cannot be executed’*
*‘Export Jobs Still Running. Currently selected Import Configuration cannot be executed’*
Figure 1a: 'Import Jobs Still Running' Error Message for Executing Imports
Figure 1a: 'Import Jobs Still Running' Error Message for Executing Exports
### **Environment**
All SAP environments
### **Cause**
A different configuration is still being processed. FLUX does not allow starting a new export or import while another configuration’s jobs are running in the system.
### **Resolution**
Wait for the current export or import jobs to finish before submitting a new configuration. You can check the job log by double-clicking on each package or check the job status by using tcode SM37 to confirm completion.
Once all running jobs are finished, resubmit the configuration.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.itconductor.com/user-guide/flux/troubleshooting-guide/jobs-running-error.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
