Developer forum

Forum » Integration » Job fails when ran as scheduled task

Job fails when ran as scheduled task

E-mail notifications
Imar Spaanjaars Dynamicweb Employee
Imar Spaanjaars
Reply
Posted on 23/09/2025 16:01:02

Hi there,

I have a migrated job from DW9 to 10. When I run the job directly, it succeeds. However, when ran from a scheduled task using "Import data with custom request" add-in it fails with the following:

2025-09-23 14:48:37.4798|DataIntegration|INFORMATION|reading configuration
2025-09-23 14:48:40.0524|DataIntegration|ERROR|Source table(EcomProducts) has column mappings: ProductVariantCounter that does not exists in the schema
2025-09-23 14:48:40.0527|DataIntegration|ERROR|Source table(EcomProducts) has column mappings: ProductVariantCounter that does not exists in the schema
2025-09-23 14:48:40.0535|DataIntegration|ERROR|Job failed.

My job does not map this column directly, so I am not sure what this error means. I tried refreshing the schema and then looked in the job's XML. The only reference to ProductVariantCounter is this:

<column type="Dynamicweb.DataIntegration.ProviderHelpers.SqlColumn" columnType="Dynamicweb.DataIntegration.ProviderHelpers.SqlColumn">
  <name>ProductVariantCounter</name>
  <type>System.Int32</type>
  <isNew>False</isNew>
  <limit>0</limit>
  <isIdentity>False</isIdentity>
  <sqlDbType>Int</sqlDbType>
  <isPrimaryKey>False</isPrimaryKey>
</column>

Any idea what I can do about this? Could it be a schema cache? I am not using central schema management yet. Should I?
Imar


Replies

 
Imar Spaanjaars Dynamicweb Employee
Imar Spaanjaars
Posted on 23/09/2025 16:47:54
Reply

FYI: I just created a new, simple XML to Ecom job from scratch and it has the same behavior: it works when ran as a job, but fails when ran as a task. The scheduled task uses paging so maybe it's related to that?

 
Dmitriy Benyuk Dynamicweb Employee
Dmitriy Benyuk
Posted on 23/09/2025 18:32:19
Reply

Hi Imar,
that is a bug and will be fixed asap. It is caused by the additional validation added in the job running so once the addin that uses the same job instance calls run method again and again the validation is still made and for the EcomProvider case it auto adds some virtual columns into the mappings in order it to work and then that causes the issue in the validation.
BR, Dmitrij

 
Imar Spaanjaars Dynamicweb Employee
Imar Spaanjaars
Posted on 23/09/2025 19:38:46
Reply

Thanks for the explanation, Dmitriy, much appreciated. Do you happen to have a bug number I can track?

 
Dmitriy Benyuk Dynamicweb Employee
Dmitriy Benyuk
Posted on 24/09/2025 08:42:55
Reply

Hi Imar,
yes, #25645
BR, Dmitrij

 

You must be logged in to post in the forum